Chromium freezes when a network change is detected after resuming from sleep mode. Most of the times it manages to freeze KDE. Only mouse cursor moves, but nothing else is usable, and only reboot helps. - Steps to reproduce: - Use Chromium - Sleep & Unplug network - Either: - Resume & Plug new network, or - Plug new network & Resume - Chromium will freeze shortly Most often KDE freezes, too (Can't tell which component exactly, though) Only way to prevent KDE and Chrome from freezing appears to be the following: - Use Chromium - Kill Chromium - Sleep & Unplug network - Resume with NO NETWORK - Start Chromium, reopen lost tabs (CTRL-SHIFT-T) - Plug new network There is an old bug reported on Chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=156038 However, despite Google's reluctance to fix it (It's a won't fix bug!), this should really, really not cause KDE to freeze.
Reassigning to more general component. No indication that this is an issue in KWin.
I do not see how Chromium freezes is a bug that should be handled in the KDE bug tracker. The Chromium report you mentioned was reported for Windows, and is several years old, so you should file a new Chromium ticket with _your_ issue.
I agree and understand if Chromium freezes on its own it's clearly a Chromium issue. However, if the whole of KDE freezes as a result, there may be room for improvement in KDE, as well. As a user I would expect to be able to kill the application. Normally, frozen applications cause a pop-up window to appear, confirm it is not responding, and ask if I want to wait longer or kill it. The bug I linked above is for reference and context. Reported on Windows, but also happening on Linux if you read through the comments. They just didn't bother fixing it, apparently.