Bug 488062

Summary: Extreme CPU Usage by Kwin_X11
Product: [Plasma] kwin Reporter: bugreporting
Component: performanceAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: kde, nicolas.fella, rpbikker
Priority: NOR    
Version First Reported In: 6.0.5   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description bugreporting 2024-06-05 10:39:45 UTC
SUMMARY
***
Kwin_X11 constantly uses ridiculous amount of CPU. In extreme cases 60%. Must be dealt with top priority.
***

STEPS TO REPRODUCE
1. Open 50fps avc1 video via SMPlayer/mpv
2. Watch it in a) a window b) full screen
3. click Konsole (you removed ctrl+at+t, not my fault, you have to click, or type...)
5. type "top" (don't use htop, it calculates wrong...).

OBSERVED RESULT
Unacceptable extreme use of CPU by Kwin_X11


EXPECTED RESULT:

1. Revert the regression to make kwin operate as smoothly as in the times of KDE 5.x. This regression puts kwin and by extension, the whole KDE6 in an alpha stage "class". This is just Intel only, not even a "brand new, fancy" Nvidia/AMD/AMD APU. Just Intel.

Imagine this: kwin in current state and non-gpu-accelerated video (eg. AV1) and you have "kswapd0" disaster with lockdown/total freeze, even with zswap with z3fold (to which you should switch instead of using the wrong default) allocator and early module load of LZ4 (not zstd, which is the wrong default again, because of RAM and CPU usage,...).

2. Reinstate the settings of kwin in system setting (regression of settings, now its impossible to set any parameters of the compositor, the settings were completely removed in KDE6 - users can't chose Open GL version or set any other parameters, user doesn't know if kwin is using OpenGL v2 or 3. There are zero settings* , e.g. speed/smoothness trade-off settings were removed, but even if the the "trade-off" settings were there, in KD5 in the "smoothest" settings kwin was never eating CPU or like in this KDE6 case, kwin in KDE5 had never had a "CPU leakage"/constant CPU drainage). This is wrong, really wrong. 



SOFTWARE/OS VERSIONS
pacman -Qs:
local/kwin 6.0.5-2 (plasma) [older versions from KDE6 too]
local/kwindowsystem 6.2.0-1 (kf6)
local/kwindowsystem5 5.116.0-1 (kf5)

KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.6.32-1-lts/6.8.x/6.9.x (6.9.x has nasty bugs...)
Graphics Platform: X11
Memory: 3.7 GiB of RAM
Graphics Processor: Mesa Intel HD

====
asterix notations:
*All was purposely removed to cater to the lowest "MS dumb user denominator" (just like double click instead of single click and "folder layout" instead of "desktop"; please don't put any distro users in the same category...!)
**KDE users use krunner and home folder (often on separate block device).
Comment 1 David Edmundson 2024-06-05 12:31:23 UTC
This is not a widespread issue, and not reproducible.

Lets focus on identifying what's wrong in your case rather than distracting that with any other noise in your opening thread.

 - Can you confirm if this issue persists with any kwin scripts disabled and the effects disabled.
 - Was the high CPU with both windowed and full screen modes?
 - Is this high from login or is there some other trigger?
Comment 2 Reinier 2024-06-05 19:24:08 UTC
Could this be the same as https://bugs.kde.org/show_bug.cgi?id=487895 ?
Comment 3 Bug Janitor Service 2024-06-20 03:47:15 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2024-07-05 03:47:34 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!