Summary: | KWin randomly becomes terribly slow | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Ilya Bizyaev <bizyaev> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | normal | CC: | nate |
Priority: | HI | ||
Version: | 5.18.90 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Ilya Bizyaev
2020-06-08 11:50:11 UTC
Replacing KWin seems to also help now; didn't help earlier, maybe is somehow related to x11 downgrade. Anyway, I have found one way to consistently reproduce this on my machine: restore and then maximize Firefox with CSD enabled by dragging its headerbar to the top edge. The key seems to be in the maximize animation itself, when kwin animates the future region for the app. Just reproduced with Telegram as well. > affect the mouse cursor, but it always affects window contents.
Urgh, it could be that I broke it.... :/
Do you see some other unusual things, e.g. high CPU usage, etc?
> Do you see some other unusual things, e.g. high CPU usage, etc? No, as I mentioned, all observable resources are fine... But I managed to find the reason: the issue was somehow caused by a popular KWin script called Parachute (https://github.com/tcorreabr/Parachute). Disabling it fixes the problem for me, and re-enabling returns it. I don't know though if it's a bug in the script or in KWin itself. I'd start with Parachute. IIRC the developers is aware that it's implemented in an inefficient way right now. He might be open to assistance on that front. See https://phabricator.kde.org/T13224 I suspect there's some KWin bug still involved here since the issue occurs when the effect shouldn't even be triggered and persists for the whole session afterward. But I don't know enough of what KWin scripting API allows to do to be sure. |