Resolved: Window server hanging after sleep - 13.1 Beta

[haralds]

With the later 13.0 Beta (22A5373b) I am experiencing the GUI being unresponsive to clicks or keystrokes after long (?) sleep. I have to log in via ssh and force a logout of the GUI user to recover.
Is anybody else seeing this.
It could also be caused by one of my apps. Sensei Monitor is not running properly so it could be the culprit.

 

[solouki]

Hi haralds,

I don't know if it is the same thing or not, but I've been experiencing unresponsive GUI troubles after being woken from sleep, especially with regards to Mission Control and switching Desktops (Spaces) for a number of the developer Ventura Betas, not just the last one. At times these result in a WindowServer timeout and crash, that also sometimes result in a kernel panic. I found, however, by looking through logs that instead of allowing these "slowdowns" to proceed, if I quickly killed the Dock (killall -9 Dock) that this recovered the WindowServer and the OS went back to its normal responsiveness without having to logout of the user.

...just my GUI troubles and a partial bandaid "work-around" ... Good luck.

 

[haralds]

When hung like this, the system does not respond to the keyboard or mouse click event. So I cannot do anything. I might try to kill the dock from SSH. Faster than logging out.
Separate from that the BlueTooth mouse/keyboard/trackpad also occasionally disconnect and then reconnect after tapping & clicking.

 

[haralds]

Appears fixed in RC1.

 

[solouki]

Yes, running RC2 and haven't yet had a WindowServer crash. I'm crossing my fingers and hoping that they won't reoccur.

 

[haralds]

Appears fixed in RC1.

Nope. Not working. Always hangs or becomes completely unresponsive on sleep.

 

[haralds]

This is still an issue with the Release version after a full install. It only hangs on long sleep in the morning hours.
Could it be some maintenance task?

 

[haralds]

I finally caught it in the act by leaving the Activity Monitor open with the top % CPU at the top. SoundSource was saturating a couple of CPU cores.
It turns out to be the "Super Volume Keys" feature that taps into the keyboard shortcuts! First not running it and then running it and turning the feature off removed the problem.
Testing a Rogue Amoeba Dev build now to see if it's fixed.

 

[jvlfilms]

I am unfortunately experiencing this as well but can't seem to find my culprit so far....