https://bugs.kde.org/show_bug.cgi?id=475322
--- Comment #18 from fililip <t...@nitrosubs.live> --- Yeah, you're right, that makes sense. I came back to this issue, played with resets a bit more and noticed something odd with this hang: 1) I started a new, clean session, 2) I launched vkcube, 3) I triggered a reset with debugfs, the desktop recovered properly, the vkcube window became stuck, but no hang yet (that's why you might have gotten no coredump before), 4) I then attempted to move the vkcube window (with the Super + left mouse button combo) and immediately (a few frames later) got a hang. I presume this is when Xwayland crashed and became a zombie process. This feels like KWin is trying to process an event for Xwayland but fails and waits indefinitely (maybe for the event sockets that don't get a chance to unregister in time?). I'm also able to trigger this hang without a GPU reset by simply doing killall -9 Xwayland a few times rapidly after starting a new session, which suggests this is not just a graphics reset issue. Though this method only works sometimes, it doesn't hang all the time. (But the hang itself also seems non-deterministic, since I've also managed to crash Xwayland with a graphics reset without it blocking anything.) Some time ago you mentioned timing the blur effect out when it takes too long to execute. Would it be possible to do something similar for Xwayland, so that when it crashes and enters the zombie state, KWin can continue to function, or would that break functionality in some X11 apps (like games that freeze for a bit when loading/processing shaders that might be unnecessarily killed by such mechanism)? -- You are receiving this mail because: You are watching all bug changes.
