Bug 500792

Summary: kwin_wayland uses enormous amount of memory
Product: [Plasma] kwin Reporter: elman <elman>
Component: performanceAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: john.kizer, nate
Priority: NOR    
Version First Reported In: 6.3.1   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: btop
pmap

Description elman 2025-02-26 23:06:10 UTC
Created attachment 178931 [details]
btop

SUMMARY
I have a problem with kwin_wayland. Over time, it uses more and more memory until system starts swapping and becomes unresponsive. This is very noticeable when I do web coding. I use JetBrains IDE and Firefox browser. I have these apps opened for a longer period of time (today it's for 2 hours), and eventually I have to restart my laptop because it becomes sooo slow.

I have 32 GB of RAM, so that shouldn't be an issue. When I close all apps, kwin_wayland still sits on that memory and won't release it. I use built-in 4K screen with HDR + 2K external screen.

Is there any way I could obtain more insights into what's happening and to send it to you?

STEPS TO REPRODUCE
1. For me just use JetBrains IDE + Firefox for longer period of time.

OBSERVED RESULT
Computer slow down until it's unusable and must be rebooted.

EXPECTED RESULT
No slow-downs.

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.4-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics
Memory: 30.8 GiB of RAM
Graphics Processor 1: AMD Radeon Graphics
Graphics Processor 2: llvmpipe
Comment 1 elman 2025-02-26 23:15:01 UTC
Created attachment 178932 [details]
pmap
Comment 2 John Kizer 2025-03-15 22:17:29 UTC
Hi - merging this in with an existing bug report where investigation has been going on into kwin_wayland memory leaks with multi-screen setups. Thanks!

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