https://bugs.kde.org/show_bug.cgi?id=491226
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
--- Comment #3 from Harald Sitter <sit...@kde.org> ---
https://invent.kde.org/sitter/crashinator/-/commit/03f174adb7c7905f42df57ef221d062a2e7ac767
Glancing at the code that has to do with how we detect ANR on wayland. We send
a ping to the surface when either the window gets focus or a window close is
issued.
You can actually see that very well in crashinator.
- If you trigger a hang and do absolutely nothing (outside) the window will
**not** turn unresponsive at all because kwin never sent a ping.
- If you trigger a hang and change focus away and back, the window will turn
unresponsive.
- If you then do absolutely nothing again the window will stay unresponsive
even after having recovered.
- If you then again do a focus change the window will turn responsive again.
`crashinator --platform xcb` meanwhile never detects the window as unresponsive
unless you click close and then obviously it closes once it turns responsive
again. We just outright have no means to detect unresponsive windows outside
the close scenario.
That said, the trouble appears to be that the the ever so late pong is
eventually ignored by handlePongReceived because handlePingTimeout erased the
serial and handlePongReceived was changed to only turn windows responsive if
the serial is in m_pings.
--
You are receiving this mail because:
You are watching all bug changes.
