You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this regressed during swaywm/wlroots@eb22ae9; the prior commit does not exhibit the same behavior. Filing under Sway since I think Sway's responsible for CSDs.
To reproduce, have a config with default_border pixel. Start kitty (latest version), and float it.
Run
for i in `seq 1 50`; do swaymsg border pixel && swaymsg border csd; done
Observe as window grows in size and becomes corrupted with the previous CSDs.
Note that on GNOME, which I understand is CSD-only, there are no borders of any kind around the window.
For extra wonkiness at this point, fullscreen kitty. Sway will start consuming a lot of CPU and become semi-unresponsive as it gets into some sort of feedback loop where the kitty window continues to grow far past the screen boundaries. Logs at this point contain a flood of
04:28:47.683 [sway/desktop/transaction.c:415] Transaction 0x558726dfde00 committing with 1 instructions
04:28:47.683 [sway/desktop/transaction.c:492] Transaction 0x558726dfde00 is ready
04:28:47.683 [sway/desktop/transaction.c:281] Applying transaction 0x558726dfde00
04:28:47.685 [sway/desktop/transaction.c:415] Transaction 0x5587264654c0 committing with 1 instructions
04:28:47.685 [sway/desktop/transaction.c:492] Transaction 0x5587264654c0 is ready
04:28:47.685 [sway/desktop/transaction.c:281] Applying transaction 0x5587264654c0
WAYLAND_DEBUG logs show Sway sending a ton of xdg_toplevel.configure events with ever-increasing dimensions.
I believe this regressed during swaywm/wlroots@eb22ae9; the prior commit does not exhibit the same behavior. Filing under Sway since I think Sway's responsible for CSDs.
To reproduce, have a config with
default_border pixel
. Startkitty
(latest version), and float it.Run
Observe as window grows in size and becomes corrupted with the previous CSDs.
Note that on GNOME, which I understand is CSD-only, there are no borders of any kind around the window.
For extra wonkiness at this point, fullscreen
kitty
. Sway will start consuming a lot of CPU and become semi-unresponsive as it gets into some sort of feedback loop where thekitty
window continues to grow far past the screen boundaries. Logs at this point contain a flood ofWAYLAND_DEBUG
logs show Sway sending a ton ofxdg_toplevel.configure
events with ever-increasing dimensions.WAYLAND_DEBUG log
The text was updated successfully, but these errors were encountered: