Crash with single-instance mode on displays with different scale factors about kitty HOT 5 CLOSED

Doesnt reproduce for me with those steps, post the backtrace from the
crash.

from kitty.

After running in a debugger, it looks like it's not actually crashing but instead exiting normally. However it does print this before it exits:

wl_surface@23: error 2: Buffer size (778x321) is not divisible by scale (2)
[359 23:48:18.371285] [glfw error 65544]: Wayland: fatal display error: Protocol error
[Thread 0x7f2a737fe6c0 (LWP 127425) exited]
[Thread 0x7f2a73fff6c0 (LWP 127424) exited]
[Thread 0x7f2a7bfff6c0 (LWP 127413) exited]
[Thread 0x7f2a88dbc6c0 (LWP 127412) exited]
[Thread 0x7f2a7a3fd6c0 (LWP 127415) exited]
[Thread 0x7f2a7abfe6c0 (LWP 127414) exited]
[Thread 0x7f2a895bd6c0 (LWP 127411) exited]
[Thread 0x7f2a89dbe6c0 (LWP 127410) exited]
[Inferior 1 (process 127409) exited normally]

from kitty.

Seems like the size of the window is relevant. I should have mentioned earlier that I'm dragging a sway floating window across the displays.

from kitty.

Ah, Wayland. The gift that keeps on giving. I'm afraid I don't have the
time/interest to work on this. But PRs are welcome, relevant code is in
glfw/wl_window.c you will most likely need to resize the window to the
closest multiple of the scale of both monitors in
dispatchChangesAfterConfigure. This is pretty poor design in Wayland,
since resizing windows while dragging them around is absolutely not
expected behavior.

from kitty.

And actually thinking about this some more, I cant believe the right solution is for applications to resize their windows while being dragged around. Maybe report the issue to sway and see what they suggest.

from kitty.