Bug 503184

Summary: Unjustified High CPU of kwin_wayland after logging in
Product: [Plasma] kwin Reporter: Adam <skiba.adam>
Component: performanceAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kdedev
Priority: NOR    
Version First Reported In: 6.3.4   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=486214
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Screen from btop command

Description Adam 2025-04-22 17:23:34 UTC
SUMMARY
Hey Team, after startup process kwin_wayland is having constantly quite high CPU usage (approx 63% of single 3Ghz core), after killing it compositor(?) restarts with kwin_wayland "idling" at CPU 0-3%

STEPS TO REPRODUCE
1. Login into Plasma

OBSERVED RESULT
With second monitor plugged in via USBC:
approx 63% of single 3Ghz core for process:
/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_rcGssW --xwayland

Without second montior 
approx 13% of single 3Ghz core for process
/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_rcGssW --xwayland
but when I plugin second monitor it jumps to 63%

In both cases, killing it will make it idling (0-3%)


EXPECTED RESULT
kwin_wayland "idling" at CPU 0-3%

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.13.12-x64v3-xanmod1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor 1: AMD Radeon Graphics
Graphics Processor 2: zink Vulkan 1.3
Comment 1 Adam 2025-04-22 17:27:10 UTC
Created attachment 180529 [details]
Screen from btop command
Comment 2 TraceyC 2025-04-22 19:33:42 UTC
This looks like the same issue as bug 486214. Please follow that report for updates. Thanks.

*** This bug has been marked as a duplicate of bug 486214 ***