https://bugs.kde.org/show_bug.cgi?id=498297
Bug ID: 498297
Summary: High CPU & memory usage on kwin_wayland
Classification: Plasma
Product: kwin
Version: 6.2.5
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: performance
Assignee: kwin-bugs-n...@kde.org
Reporter: matthewbis...@gmail.com
Target Milestone: ---
Created attachment 177135
--> https://bugs.kde.org/attachment.cgi?id=177135&action=edit
screenshot
SUMMARY
I would say for about 4 months now, kwin_wayland takes an insane amount of
memory 8-10gb! Initially, after kwin would take about 8-8.2gb of memory, it
would become slow, and then crash! In the more recent kernel versions (at the
moment 6.12.8-2-cachyos), the system doesn't crash but when it reaches 10gb its
completely unresponsive and I have to force reboot.
STEPS TO REPRODUCE
There arent really any specific steps that cause this issue. It just happens
when it happens. Usually after a couple of hours of browsing.
OBSERVED RESULT
Initially the system works fine and is responsive. After a few hours you will
feel like the system is slow, and there are frame drops, after which you will
open the process manager (like btop) and will observe kwin using 8-10 gb of
memory. I have attached a screenshot:
I also have a (somewhat) older bug report that might give you bit more insight:
https://paste.cachyos.org/p/25bf4f9.log
This bug report is from when my system crashed after 8gb. I havent been able to
create a newer bugreport yet because by the time I feel like lag, my system
starts becoming unresposive.
EXPECTED RESULT
Obviously the expected result is for this not to happen. In other words, stable
performance
Operating System: CachyOS Linux
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.12.8-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i9-12900H
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Xe Graphics
(also have rtx 3070-ti but kinfo doesnt display it)
ADDITIONAL INFORMATION
Also saw this kde bug report:
https://bugs.kde.org/show_bug.cgi?id=496469#add_comment, its similar to mine,
but im not disconnecting any monitors (although i am connected to one though).
Furthermore, its marked as resolved, so they are *probably* not related, but I
though it would be good if I mentioned it.
Thank you for having a look
--
You are receiving this mail because:
You are watching all bug changes.
