Bug 502259

Summary: Extreme memory leakage when using KDE with kwin_wayland in multi-monitor setup
Product: [Plasma] kwin Reporter: filip <filipembedded>
Component: multi-screenAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nicolas.fella, xaver.hugl
Priority: NOR    
Version First Reported In: 6.3.3   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description filip 2025-03-31 21:06:04 UTC
SUMMARY
I have noticed that something has been leaking memory on my laptop. I noticed it first time when my laptop started crashing and glitching, I checked htop and have seen that my RAM usage has been maxed out. After some further investigation, I noticed that it occurs when I plug in my HDMI cable of my external monitor. After some time, the memory starts to leak a lot. I figured out that when I unplug my HDMI cable the memory is not freed, but when I plug it back I noticed that memory usage drops in that moment (like something reallocates used memory).  However, on the other side, when I reboot the laptop with cable already plugged in, I don't see that memory leakage anymore. Like there is a problem with the plugging and unplugging the HDMI cable. 

STEPS TO REPRODUCE
1. Power on the laptop with the unplugged HDMI cable
2. Power up the monitor with the cable unplugged from monitor
3. Plug in the cable and open some tabs in Browser (or anything else that will faster consume some memory)

EXPECTED RESULT
After 10-20 minutes, the leakage should be noticed. The used memory will only rise.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Arch Linux 
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.3

ADDITIONAL INFORMATION
Laptop: HP Pavilion Gaming 
Processor: AMD Ryzen 5600H 
GPU: NVidia GeForce GTX 1650
External monitor: LG FLATRON W2243S-PF
Comment 1 filip 2025-03-31 21:08:14 UTC
I forgot to mention that kwin_wayland is leaking the memory.
Comment 2 Zamundaaa 2025-03-31 21:54:09 UTC

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