SUMMARY Since about a month kwin_wayland here: 1) Uses more and more memory after external monitors have been disconnected and reconnected 2) Randomly freezes image output on one or all external monitors kwin_wayland --replace helps. STEPS TO REPRODUCE For the case (1) 1. Disconnect both external monitors, so that laptop turns on internal monitor 2. Reconnect the external monitors (the internal monitor switches off) 3. Wait, browse web pages, watch movies, etc. - the kwin_wayland process will start utilising more and more memory For the case (2) 1. Don't know. I am not sure what triggers the stop of updating of image on one of the monitors. OBSERVED RESULT Case (1) - the kwin_wayland process will start utilising more and more memory Case (2) - image on one or both external monitors stop updating. Attempting to disconnect one of the monitors hangs the system or image updates completely - only "REISUB" seems to help EXPECTED RESULT Stable performance of Plasma. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.7.2 Kernel Version: 6.11.8-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 7940HS w/ Radeon 780M Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon 780M ADDITIONAL INFORMATION This is an Optimus laptop ASUS TUF Gaming A15 FA507XI_FA507XI with laptop NVidia RTX 4070. One external monitor is connected through HDMI, the other one through USB-C->DP. I am not sure what caused the problem, since 3 things happened in very close moments: 1. Plasma update 2. Kernel update 3. NVidia drivers update
I can confirm this. KWin ate more than 12GB of my memory oO Operating System: Arch Linux KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.11.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-10850H CPU @ 2.70GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics, external monitor is connected through Nvidia card though GP2: NVIDIA GeForce GTX 1650 Ti with Max-Q Design Manufacturer: LENOVO Product Name: 20TKCTO1WW System Version: ThinkPad X1 Extreme Gen 3 11月 21 19:26:17 workpad kernel: Out of memory: Killed process 1077 (kwin_wayland) total-vm:16333436kB, anon-rss:182896kB, file-rss:12580488kB, shmem-rss:451928kB, UID:1000 pgtables:27612kB oom_score_adj:200 11月 21 19:26:17 workpad kernel: WebExtensions[3114]: segfault at 0 ip 00007467e66005a1 sp 00007ffd65ca87a0 error 6 in libxul.so[55ff5a1,7467e2afe000+5ec4000] likely on CPU 8 (core 2, socket 0) 11月 21 19:26:17 workpad kernel: Code: 8b 04 25 28 00 00 00 48 3b 44 24 28 75 2d 48 83 c4 30 5b 41 5e 5d c3 48 8b 3b ff 15 11 b9 86 02 48 8b 0d 1a b6 86 02 48 89 01 <c7> 04 25 00 00 00 00 b2 00 00 00 ff 15 0e b6 86 02 e8 f9 09 3c 02 11月 21 19:26:18 workpad systemd-journald[429]: Under memory pressure, flushing caches. 11月 21 19:26:03 workpad kwin_wayland[1077]: kwin_wayland_drm: Pageflip timed out! This is a kernel bug
Same thing happening on my system. Operating System: Arch Linux KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.12.1-2-cachyos (64-bit) Graphics Platform: Wayland Processors: Ryzen 7 5800H Memory: 16GB Graphics Processor: RTX 3060, external monitor uses that Manufacturer: HP Product Name: Omen 15.6"
Is it possible that kwin developers to look into this? Using KDE now with multiple monitors is like moving into lovely Windows 95 times, with 2 Plasma restarts per day...
There's a high chance this is fixed by https://invent.kde.org/plasma/kwin/-/merge_requests/6845, so I'm closing this. If it still happens in 6.2.5, just reopen this bug report!
(In reply to Zamundaaa from comment #4) > There's a high chance this is fixed by > https://invent.kde.org/plasma/kwin/-/merge_requests/6845, so I'm closing > this. If it still happens in 6.2.5, just reopen this bug report! Thank you. Will check when 6.2.5 reaches Fedora.
I really hope that solves it and 6.2.5 gets released soon. I noticed that KWin returns it's memory if the second screen gets replugged after getting unplugged once (physically pulling the HDMI cable). Not a nice workaround, but better than having to log in again.
(In reply to sowieso from comment #6) > I really hope that solves it and 6.2.5 gets released soon. > I noticed that KWin returns it's memory if the second screen gets replugged > after getting unplugged once (physically pulling the HDMI cable). > Not a nice workaround, but better than having to log in again. I've noticed something like that too, although not tested extensively. However, I notice some lagging after these operations. Not sure it is related, so I am waiting for solving this bug before (hopefully not) reporting more.
This issue is still present on 6.2.5. kwin_wayland reached a 10GB usage as per btop at one point.
I can confirm, that the issue is still present in KDE 6.2.5 on Fedora 40, making KDE barely usable on my multi-monitor NVidia Optimus laptop setup. Perhaps I'll find a way to downgrade it to 6.2.3 or it will work better on X...
I can also confirm that this is still present in kwin_wayland 6.2.5. In my case, the memory consumption is rising at around 3 GB per second. Unplugging the HDMI cable and plugging it back in indeed causes the memory to be released (thanks, sowieso@dukun.de). Operating System: Fedora Linux 41 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.1 Kernel Version: 6.12.7-200.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i9-12900H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Iris® Xe Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: Stealth GS66 12UH System Version: REV:1.0
(In reply to Roman Teterin from comment #10) > I can also confirm that this is still present in kwin_wayland 6.2.5. > In my case, the memory consumption is rising at around 3 GB per second. > Unplugging the HDMI cable and plugging it back in indeed causes the memory > to be released (thanks, sowieso@dukun.de). > > Operating System: Fedora Linux 41 > KDE Plasma Version: 6.2.5 > KDE Frameworks Version: 6.9.0 > Qt Version: 6.8.1 > Kernel Version: 6.12.7-200.fc41.x86_64 (64-bit) > Graphics Platform: Wayland > Processors: 20 × 12th Gen Intel® Core™ i9-12900H > Memory: 31.0 GiB of RAM > Graphics Processor: Mesa Intel® Iris® Xe Graphics > Manufacturer: Micro-Star International Co., Ltd. > Product Name: Stealth GS66 12UH > System Version: REV:1.0 Sorry, I meant 3 GB per hour, of course.
Created attachment 177296 [details] journalctl output
Above is the log generated with sudo journalctl --boot 0 --grep=nvidia >> nvidia-memory-leak-log.txt && sudo journalctl --boot 0 --identifier=kwin_wayland >> nvidia-memory-leak-log.txt && sudo journalctl --boot 0 --identifier=kwin_wayland_wrapper >> nvidia-memory-leak-log.txt as given in https://bugs.kde.org/show_bug.cgi?id=496898. The relevant part starts on 12 Jan 10:35, as it is when I woke up my laptop.
Could you update us if anyone is trying to fix this issue? This is important, because due to the very serious nature of this instability and the level of unusability it causes, we may have to start looking for an alternative to KDE if no fix is planned in the near future...
I have tried to reproduce the issue, but it doesn't happen here, with Intel + NVidia. Memory usage stayed very constant at about 320MiB while using the external monitor and letting glxgears spin on the external monitor for two hours to ensure whatever small leak could happen would actually be visible.
And I assume you tested it after waking up from sleep? The fact that it happens for several people would suggest a difference in configuration (maybe it has to be AMD+Nvidia?)
(In reply to Zamundaaa from comment #15) > I have tried to reproduce the issue, but it doesn't happen here, with Intel > + NVidia. Memory usage stayed very constant at about 320MiB while using the > external monitor and letting glxgears spin on the external monitor for two > hours to ensure whatever small leak could happen would actually be visible. I have Intel + Nvidia notebook
Could everyone that has the issue please comment the NVidia driver version they're using? On this laptop I have driver version 565.77-12, on kernel 6.12.10
(In reply to Zamundaaa from comment #15) > I have tried to reproduce the issue, but it doesn't happen here, with Intel > + NVidia. Memory usage stayed very constant at about 320MiB while using the > external monitor and letting glxgears spin on the external monitor for two > hours to ensure whatever small leak could happen would actually be visible. I have an Dell WD15 dock, the monitor is connected to it using HDMI and then dock's Type-C cable is connected to the laptop. As I use this dock for work also, so I quite often would switch out my work laptop with my own laptop on the dock. So everytime make the switch - disconnect my own laptop, connect the work laptop and after work disconnect the work laptop and connect my own, wake it up from sleep, the memory leak happens. But a simple kwin_wayland --replace fixes it. I'm on NVIDIA 565.77-263
I wonder if something like how the HDMI output port is routed has an impact. Is it wired directly to the dGPU or through the iGPU.
(In reply to Zamundaaa from comment #18) > Could everyone that has the issue please comment the NVidia driver version > they're using? > > On this laptop I have driver version 565.77-12, on kernel 6.12.10 I have 565.77 (not sure how to get subnumber) on kernel 6.12.8-100.fc40.x86_64
okay, so it's probably not the driver version. (In reply to righn from comment #19) > I have an Dell WD15 dock, the monitor is connected to it using HDMI and then > dock's Type-C cable is connected to the laptop. As I use this dock for work > also, so I quite often would switch out my work laptop with my own laptop on > the dock. So everytime make the switch - disconnect my own laptop, connect > the work laptop and after work disconnect the work laptop and connect my > own, wake it up from sleep, the memory leak happens. But a simple > kwin_wayland --replace fixes it. > > I'm on NVIDIA 565.77-263 How much memory is leaked when you unplug the screen / how much memory usage does KWin gain on re-plug?
(In reply to Zamundaaa from comment #22) > okay, so it's probably not the driver version. > > (In reply to righn from comment #19) > > I have an Dell WD15 dock, the monitor is connected to it using HDMI and then > > dock's Type-C cable is connected to the laptop. As I use this dock for work > > also, so I quite often would switch out my work laptop with my own laptop on > > the dock. So everytime make the switch - disconnect my own laptop, connect > > the work laptop and after work disconnect the work laptop and connect my > > own, wake it up from sleep, the memory leak happens. But a simple > > kwin_wayland --replace fixes it. > > > > I'm on NVIDIA 565.77-263 > How much memory is leaked when you unplug the screen / how much memory usage > does KWin gain on re-plug? It happens gradually. For example, right now, I unplugged the screen - kwin_wayland used about 290MB, replugged it, it started at about 320MB and starts increasing gradually. While I was writing this comment, it already increased by 100MB, so it's at 440MB already.
Here it depends on how I am using the machine. If I leave it be, kwin_wayland may gain a few GB in a few hours. If I use it, for example for web browsing, it may gain the same amount in one hour.
(In reply to Zamundaaa from comment #18) > Could everyone that has the issue please comment the NVidia driver version > they're using? > > On this laptop I have driver version 565.77-12, on kernel 6.12.10 On my laptop I have version 565.77-3, kernel 6.12.9-200. Disconnected and re-connected the external monitor 15 minutes ago, just to make sure that the issue is still present. Memory usage dropped from 440 to around 380 MB and then started to rise gradually. Now it's at 1 GB and is still rising.
Okay, maybe the import mode could be different. Please put > QT_LOGGING_RULES="kwin_wayland_*.debug=true" into /etc/environment, reboot, connect the external monitor and check the output of > journalctl --user-unit plasma-kwin_wayland --boot 0 | grep import for which multi-gpu copy mode your system is using, and > wayland-info | grep NVIDIA and > wayland-info | grep INTEL (or AMD) for which GPU is the primary one on your system
journalctl --user-unit plasma-kwin_wayland --boot 0 | grep import Journal file /var/log/journal/49739eb258bf4717b5bb4420280b45ab/system@000629a3af917a7a-efdf6713f41a1159.journal~ is truncated, ignoring file. Jan 24 19:27:45 lwpcomp4 kwin_wayland[3128]: kwin_wayland_drm: chose egl import with format AB30 and modifier 0 Jan 24 19:27:45 lwpcomp4 kwin_wayland[3128]: kwin_wayland_drm: chose egl import with format AB30 and modifier 0 Jan 24 19:27:54 lwpcomp4 kwin_wayland[3128]: kwin_wayland_drm: chose cpu import with format AR24 and modifier 0 Jan 24 19:27:55 lwpcomp4 kwin_wayland[3128]: kwin_wayland_drm: chose cpu import with format AR24 and modifier 0 wayland-info | grep NVIDIA gives nothing wayland-info | grep AMD 0x32335247 = 'GR32'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x32335247 = 'GR32'; 0x0200000010467b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x32335247 = 'GR32'; 0x0200000010437b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_64B,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=64B,PIPE_XOR_BITS=2 0x32335247 = 'GR32'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x32335247 = 'GR32'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x48344258 = 'XB4H'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x48344258 = 'XB4H'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x48344258 = 'XB4H'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x35314241 = 'AB15'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x35314241 = 'AB15'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x35314241 = 'AB15'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x48344241 = 'AB4H'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x48344241 = 'AB4H'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x48344241 = 'AB4H'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x35315241 = 'AR15'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x35315241 = 'AR15'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x35315241 = 'AR15'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x38344258 = 'XB48'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x38344258 = 'XB48'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x38344258 = 'XB48'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x36314752 = 'RG16'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x36314752 = 'RG16'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x36314752 = 'RG16'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x32314241 = 'AB12'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x32314241 = 'AB12'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x32314241 = 'AB12'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x38385247 = 'GR88'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x38385247 = 'GR88'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x38385247 = 'GR88'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x20203852 = 'R8 '; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x20203852 = 'R8 '; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x20203852 = 'R8 '; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x3231564e = 'NV12'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x3231564e = 'NV12'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x20363152 = 'R16 '; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x20363152 = 'R16 '; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x20363152 = 'R16 '; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x38344241 = 'AB48'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x38344241 = 'AB48'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x38344241 = 'AB48'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x32315241 = 'AR12'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x32315241 = 'AR12'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x32315241 = 'AR12'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x34324241 = 'AB24'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x34324241 = 'AB24'; 0x0200000010467b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x34324241 = 'AB24'; 0x0200000010437b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_64B,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=64B,PIPE_XOR_BITS=2 0x34324241 = 'AB24'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x34324241 = 'AB24'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x34324258 = 'XB24'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x34324258 = 'XB24'; 0x0200000010467b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x34324258 = 'XB24'; 0x0200000010437b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_64B,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=64B,PIPE_XOR_BITS=2 0x34324258 = 'XB24'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x34324258 = 'XB24'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x34325241 = 'AR24'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x34325241 = 'AR24'; 0x0200000010467b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x34325241 = 'AR24'; 0x0200000010437b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_64B,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=64B,PIPE_XOR_BITS=2 0x34325241 = 'AR24'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x34325241 = 'AR24'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x34325258 = 'XR24'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x34325258 = 'XR24'; 0x0200000010467b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x34325258 = 'XR24'; 0x0200000010437b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_64B,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=64B,PIPE_XOR_BITS=2 0x34325258 = 'XR24'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x34325258 = 'XR24'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x30334241 = 'AB30'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x30334241 = 'AB30'; 0x0200000010467b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x30334241 = 'AB30'; 0x0200000010437b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_64B,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=64B,PIPE_XOR_BITS=2 0x30334241 = 'AB30'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x30334241 = 'AB30'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x30334258 = 'XB30'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x30334258 = 'XB30'; 0x0200000010467b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x30334258 = 'XB30'; 0x0200000010437b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_64B,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=64B,PIPE_XOR_BITS=2 0x30334258 = 'XB30'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x30334258 = 'XB30'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x30335241 = 'AR30'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x30335241 = 'AR30'; 0x0200000010467b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x30335241 = 'AR30'; 0x0200000010437b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_64B,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=64B,PIPE_XOR_BITS=2 0x30335241 = 'AR30'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x30335241 = 'AR30'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D 0x30335258 = 'XR30'; 0x020000001046bb04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_PIPE_ALIGN,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x30335258 = 'XR30'; 0x0200000010467b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=128B,PIPE_XOR_BITS=2 0x30335258 = 'XR30'; 0x0200000010437b04 = AMD_GFX11,GFX9_64K_R_X,DCC,DCC_RETILE,DCC_INDEPENDENT_64B,DCC_INDEPENDENT_128B,DCC_MAX_COMPRESSED_BLOCK=64B,PIPE_XOR_BITS=2 0x30335258 = 'XR30'; 0x0200000010401b04 = AMD_GFX11,GFX9_64K_R_X,PIPE_XOR_BITS=2 0x30335258 = 'XR30'; 0x0200000000000a04 = AMD_GFX11,GFX9_64K_D
(In reply to Zamundaaa from comment #26) > Okay, maybe the import mode could be different. Please put > > QT_LOGGING_RULES="kwin_wayland_*.debug=true" > into /etc/environment, reboot, connect the external monitor and check the > output of > > journalctl --user-unit plasma-kwin_wayland --boot 0 | grep import > for which multi-gpu copy mode your system is using, and > > wayland-info | grep NVIDIA > and > > wayland-info | grep INTEL > (or AMD) for which GPU is the primary one on your system Added the env var, rebooted, reconnected the monitor to "initiate" the memory leak and these are the results: journalctl --user-unit plasma-kwin_wayland --boot 0 | grep import saus. 24 20:32:24 archomen kwin_wayland[984]: kwin_wayland_drm: chose egl import with format AB30 and modifier 0 saus. 24 20:32:24 archomen kwin_wayland[984]: kwin_wayland_drm: chose cpu import with format AR24 and modifier 0 saus. 24 20:32:59 archomen kwin_wayland[984]: kwin_wayland_drm: chose egl import with format AB30 and modifier 0 saus. 24 20:33:11 archomen kwin_wayland[984]: kwin_wayland_drm: chose cpu import with format AR24 and modifier 0 wayland-info | grep NVIDIA empty wayland-info | grep AMD 0x35315241 = 'AR15'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x35315241 = 'AR15'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x35315241 = 'AR15'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x35315241 = 'AR15'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x35315241 = 'AR15'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x35315241 = 'AR15'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x3231564e = 'NV12'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x3231564e = 'NV12'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x3231564e = 'NV12'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x3231564e = 'NV12'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x38344241 = 'AB48'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x38344241 = 'AB48'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x38344241 = 'AB48'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x38344241 = 'AB48'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x38344241 = 'AB48'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x38344241 = 'AB48'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x32315241 = 'AR12'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x32315241 = 'AR12'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x32315241 = 'AR12'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x32315241 = 'AR12'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x32315241 = 'AR12'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x32315241 = 'AR12'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x38344258 = 'XB48'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x38344258 = 'XB48'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x38344258 = 'XB48'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x38344258 = 'XB48'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x38344258 = 'XB48'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x38344258 = 'XB48'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x32335247 = 'GR32'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x32335247 = 'GR32'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x32335247 = 'GR32'; 0x0200000440517901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_RETILE 0x32335247 = 'GR32'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x32335247 = 'GR32'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x32335247 = 'GR32'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x32335247 = 'GR32'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x20363152 = 'R16 '; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x20363152 = 'R16 '; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x20363152 = 'R16 '; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x20363152 = 'R16 '; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x20363152 = 'R16 '; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x20363152 = 'R16 '; 0x0200000000000901 = AMD_GFX9,64KB_S 0x48344241 = 'AB4H'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x48344241 = 'AB4H'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x48344241 = 'AB4H'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x48344241 = 'AB4H'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x48344241 = 'AB4H'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x48344241 = 'AB4H'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x38385247 = 'GR88'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x38385247 = 'GR88'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x38385247 = 'GR88'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x38385247 = 'GR88'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x38385247 = 'GR88'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x38385247 = 'GR88'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x32314241 = 'AB12'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x32314241 = 'AB12'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x32314241 = 'AB12'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x32314241 = 'AB12'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x32314241 = 'AB12'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x32314241 = 'AB12'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x20203852 = 'R8 '; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x20203852 = 'R8 '; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x20203852 = 'R8 '; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x20203852 = 'R8 '; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x20203852 = 'R8 '; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x20203852 = 'R8 '; 0x0200000000000901 = AMD_GFX9,64KB_S 0x36314752 = 'RG16'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x36314752 = 'RG16'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x36314752 = 'RG16'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x36314752 = 'RG16'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x36314752 = 'RG16'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x36314752 = 'RG16'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x48344258 = 'XB4H'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x48344258 = 'XB4H'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x48344258 = 'XB4H'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x48344258 = 'XB4H'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x48344258 = 'XB4H'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x48344258 = 'XB4H'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x35314241 = 'AB15'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x35314241 = 'AB15'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x35314241 = 'AB15'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x35314241 = 'AB15'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x35314241 = 'AB15'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x35314241 = 'AB15'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x34324258 = 'XB24'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x34324258 = 'XB24'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x34324258 = 'XB24'; 0x0200000440517901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_RETILE 0x34324258 = 'XB24'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x34324258 = 'XB24'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x34324258 = 'XB24'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x34324258 = 'XB24'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x34324241 = 'AB24'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x34324241 = 'AB24'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x34324241 = 'AB24'; 0x0200000440517901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_RETILE 0x34324241 = 'AB24'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x34324241 = 'AB24'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x34324241 = 'AB24'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x34324241 = 'AB24'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x34325241 = 'AR24'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x34325241 = 'AR24'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x34325241 = 'AR24'; 0x0200000440517901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_RETILE 0x34325241 = 'AR24'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x34325241 = 'AR24'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x34325241 = 'AR24'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x34325241 = 'AR24'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x34325258 = 'XR24'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x34325258 = 'XR24'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x34325258 = 'XR24'; 0x0200000440517901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_RETILE 0x34325258 = 'XR24'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x34325258 = 'XR24'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x34325258 = 'XR24'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x34325258 = 'XR24'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x30334258 = 'XB30'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x30334258 = 'XB30'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x30334258 = 'XB30'; 0x0200000440517901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_RETILE 0x30334258 = 'XB30'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x30334258 = 'XB30'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x30334258 = 'XB30'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x30334258 = 'XB30'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x30335241 = 'AR30'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x30335241 = 'AR30'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x30335241 = 'AR30'; 0x0200000440517901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_RETILE 0x30335241 = 'AR30'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x30335241 = 'AR30'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x30335241 = 'AR30'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x30335241 = 'AR30'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x30334241 = 'AB30'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x30334241 = 'AB30'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x30334241 = 'AB30'; 0x0200000440517901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_RETILE 0x30334241 = 'AB30'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x30334241 = 'AB30'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x30334241 = 'AB30'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x30334241 = 'AB30'; 0x0200000000000901 = AMD_GFX9,64KB_S 0x30335258 = 'XR30'; 0x020000044051ba01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x30335258 = 'XR30'; 0x020000044051b901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_PIPE_ALIGN 0x30335258 = 'XR30'; 0x0200000440517901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0,RB=1,PIPE=2,DCC,DCC_MAX_COMPRESSED_BLOCK=64B,DCC_INDEPENDENT_64B,DCC_CONSTANT_ENCODE,DCC_RETILE 0x30335258 = 'XR30'; 0x0200000000401a01 = AMD_GFX9,64KB_D_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x30335258 = 'XR30'; 0x0200000000401901 = AMD_GFX9,64KB_S_X,PIPE_XOR_BITS=2,BANK_XOR_BITS=0 0x30335258 = 'XR30'; 0x0200000000000a01 = AMD_GFX9,64KB_D 0x30335258 = 'XR30'; 0x0200000000000901 = AMD_GFX9,64KB_S
(In reply to Zamundaaa from comment #26) > Okay, maybe the import mode could be different. Please put > > QT_LOGGING_RULES="kwin_wayland_*.debug=true" > into /etc/environment, reboot, connect the external monitor and check the > output of > > journalctl --user-unit plasma-kwin_wayland --boot 0 | grep import > for which multi-gpu copy mode your system is using, and > > wayland-info | grep NVIDIA > and > > wayland-info | grep INTEL > (or AMD) for which GPU is the primary one on your system Here is my output: > ~ % journalctl --user-unit plasma-kwin_wayland --boot 0 | grep import > Jan 26 22:52:06 workstation-roma kwin_wayland[23538]: kwin_wayland_drm: chose egl import with format AB30 and modifier 0 > Jan 26 22:52:19 workstation-roma kwin_wayland[23538]: kwin_wayland_drm: chose cpu import with format AR24 and modifier 0 > ~ % wayland-info | grep NVIDIA > ~ % wayland-info | grep INTEL > 0x38344258 = 'XB48'; 0x0100000000000001 = INTEL_X_TILED > 0x38344258 = 'XB48'; 0x0100000000000002 = INTEL_Y_TILED > 0x38344258 = 'XB48'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x38344258 = 'XB48'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x48344258 = 'XB4H'; 0x0100000000000001 = INTEL_X_TILED > 0x48344258 = 'XB4H'; 0x0100000000000002 = INTEL_Y_TILED > 0x48344258 = 'XB4H'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x48344258 = 'XB4H'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x32335247 = 'GR32'; 0x0100000000000001 = INTEL_X_TILED > 0x32335247 = 'GR32'; 0x0100000000000002 = INTEL_Y_TILED > 0x32335247 = 'GR32'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x32335247 = 'GR32'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x20203852 = 'R8 '; 0x0100000000000001 = INTEL_X_TILED > 0x20203852 = 'R8 '; 0x0100000000000002 = INTEL_Y_TILED > 0x20203852 = 'R8 '; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x20203852 = 'R8 '; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x36314752 = 'RG16'; 0x0100000000000001 = INTEL_X_TILED > 0x36314752 = 'RG16'; 0x0100000000000002 = INTEL_Y_TILED > 0x36314752 = 'RG16'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x36314752 = 'RG16'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x35315241 = 'AR15'; 0x0100000000000001 = INTEL_X_TILED > 0x35315241 = 'AR15'; 0x0100000000000002 = INTEL_Y_TILED > 0x35315241 = 'AR15'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x35315241 = 'AR15'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x48344241 = 'AB4H'; 0x0100000000000001 = INTEL_X_TILED > 0x48344241 = 'AB4H'; 0x0100000000000002 = INTEL_Y_TILED > 0x48344241 = 'AB4H'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x48344241 = 'AB4H'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x3231564e = 'NV12'; 0x0100000000000001 = INTEL_X_TILED > 0x3231564e = 'NV12'; 0x0100000000000002 = INTEL_Y_TILED > 0x38385247 = 'GR88'; 0x0100000000000001 = INTEL_X_TILED > 0x38385247 = 'GR88'; 0x0100000000000002 = INTEL_Y_TILED > 0x38385247 = 'GR88'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x38385247 = 'GR88'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x20363152 = 'R16 '; 0x0100000000000001 = INTEL_X_TILED > 0x20363152 = 'R16 '; 0x0100000000000002 = INTEL_Y_TILED > 0x20363152 = 'R16 '; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x20363152 = 'R16 '; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x38344241 = 'AB48'; 0x0100000000000001 = INTEL_X_TILED > 0x38344241 = 'AB48'; 0x0100000000000002 = INTEL_Y_TILED > 0x38344241 = 'AB48'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x38344241 = 'AB48'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x32315241 = 'AR12'; 0x0100000000000001 = INTEL_X_TILED > 0x32315241 = 'AR12'; 0x0100000000000002 = INTEL_Y_TILED > 0x32315241 = 'AR12'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x32315241 = 'AR12'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x34324241 = 'AB24'; 0x0100000000000001 = INTEL_X_TILED > 0x34324241 = 'AB24'; 0x0100000000000002 = INTEL_Y_TILED > 0x34324241 = 'AB24'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x34324241 = 'AB24'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x34324258 = 'XB24'; 0x0100000000000001 = INTEL_X_TILED > 0x34324258 = 'XB24'; 0x0100000000000002 = INTEL_Y_TILED > 0x34324258 = 'XB24'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x34324258 = 'XB24'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x34325258 = 'XR24'; 0x0100000000000001 = INTEL_X_TILED > 0x34325258 = 'XR24'; 0x0100000000000002 = INTEL_Y_TILED > 0x34325258 = 'XR24'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x34325258 = 'XR24'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x34325241 = 'AR24'; 0x0100000000000001 = INTEL_X_TILED > 0x34325241 = 'AR24'; 0x0100000000000002 = INTEL_Y_TILED > 0x34325241 = 'AR24'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x34325241 = 'AR24'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x30335241 = 'AR30'; 0x0100000000000001 = INTEL_X_TILED > 0x30335241 = 'AR30'; 0x0100000000000002 = INTEL_Y_TILED > 0x30335241 = 'AR30'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x30335241 = 'AR30'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x30334241 = 'AB30'; 0x0100000000000001 = INTEL_X_TILED > 0x30334241 = 'AB30'; 0x0100000000000002 = INTEL_Y_TILED > 0x30334241 = 'AB30'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x30334241 = 'AB30'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC > 0x30335258 = 'XR30'; 0x0100000000000001 = INTEL_X_TILED > 0x30335258 = 'XR30'; 0x0100000000000002 = INTEL_Y_TILED > 0x30335258 = 'XR30'; 0x0100000000000006 = INTEL_Y_TILED_GEN12_RC_CCS > 0x30335258 = 'XR30'; 0x0100000000000008 = INTEL_Y_TILED_GEN12_RC_CCS_CC
Did out outputs provide any clue?
Unfortunately not, everything looks as expected and the same as on my system.
*** Bug 497056 has been marked as a duplicate of this bug. ***
*** Bug 498556 has been marked as a duplicate of this bug. ***
*** Bug 496898 has been marked as a duplicate of this bug. ***
Trying to be helpful here: - are we all using optimus with the amd/intel GPU as the main one? - do we all have the external monitor ports connected to the same GPU? - are we all having this issue only when putting the laptop to sleep and waking it up?
Coming here from https://bugs.kde.org/show_bug.cgi?id=496898 which was marked as duplicate of this issue. (In reply to Lech from comment #35) > Trying to be helpful here: > - are we all using optimus with the amd/intel GPU as the main one? AMD integrated GPU with NVidia DGPU here. > - do we all have the external monitor ports connected to the same GPU? Yes, all connected to the DGPU > - are we all having this issue only when putting the laptop to sleep and > waking it up? No for me it is triggered after plugging in an external screen while kwin_wayland is running.
(In reply to Lech from comment #35) > Trying to be helpful here: > - are we all using optimus with the amd/intel GPU as the main one? > - do we all have the external monitor ports connected to the same GPU? > - are we all having this issue only when putting the laptop to sleep and > waking it up? > - are we all using optimus with the amd/intel GPU as the main one? In my case it's AMD iGPU and NVIDIA GPU. - - do we all have the external monitor ports connected to the same GPU? Yes, all of my output ports are wired to the dGPU. > - are we all having this issue only when putting the laptop to sleep and > waking it up? Not exactly. If my external monitor stays connected at the time I put my laptop to sleep and wake it up, the leak doesn't happen. The leak only happens when I disconnect the external monitor and reconnect it, doesn't matter if it was asleep or no.
*** Bug 498627 has been marked as a duplicate of this bug. ***
An observation. Just unplugging the HDMI cable doesn't restore the memory usage. It's plugging the HDMI cable back in, that restores the usage to normal levels. Next I'll test if after removing the cable I just let the system sit, does the memory usage (a) increases (b) decreases slowly or (c) stays the same. [SPEC] Operating System: Fedora Linux 41 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.1 Kernel Version: 6.12.10-200.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx Memory: 17.4 GB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics Manufacturer: HP Product Name: HP Pavilion Gaming Laptop 15 I'm using nvidia.
(In reply to Lech from comment #35) > Trying to be helpful here: > - are we all using optimus with the amd/intel GPU as the main one? No, in my case is intel iGPU and nvidia dGPU > - do we all have the external monitor ports connected to the same GPU? Both monitors are connected to a dock and to the pc via USB-C to my laptop, and goes to dGPU (nvidia) > - are we all having this issue only when putting the laptop to sleep and > waking it up? Nop, issue can happen from a clean boot where external monitor was connected from boot (since I am using dock I am not sure what happens behind). If I can provide any more useful information I'll be glad to help.
I am also experiencing this issue and same as others, unplugging and *then* re-plugging in the video cable clears up the excessive RAM usage. I have and Asus Zephyrus G15 (2021) GA503 with an AMD Ryzen 9 5900HS CPU w/iGPU and an NVIDIA 3080 dGPU. For me, I'm using a USB C to DisplayPort adapter to connect my monitor. IIRC, on this laptop, the HDMI passes through the AMD iGPU and offloads to the NVIDIA dGPU, while the USB C DisplayPort is hardwired to the dGPU. [SPEC] Operating System: Fedora Linux 41 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.1 Kernel Version: 6.12.9-200.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 5900HS with Radeon Graphics Memory: 38.6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Zephyrus G15 GA503QS_GA503QS
(In reply to Lech from comment #35) > Trying to be helpful here: > - are we all using optimus with the amd/intel GPU as the main one? Intel iGPU and Nvidia dGPU with driver 565.77 in my case > - do we all have the external monitor ports connected to the same GPU? Using HDMI port that is connected to dGPU > - are we all having this issue only when putting the laptop to sleep and > waking it up? I experience memory leaks in two scenarios: 1. After waking up from sleep 2. After disconnecting and reconnecting external monitors Initially, I thought these scenarios were equivalent (both involving display reconnection), but comment #37 and comment #40 suggest there might be different underlying causes. I can confirm the observation from comment #24: the frequency of display repaints correlates with the rate of memory consumption, eventually using all available RAM. --- Regarding Case (2) (Display Freezing): I've also experienced the image output freezing issue mentioned in the bug description, but in my case it was specifically related to using the kzones KWin script (https://github.com/gerritdevriese/kzones). After monitor disconnection/reconnection while using this script: - ~50% of cases: Moving windows causes complete image output freeze - `kwin_wayland --replace` fails with `qt.qpa.xcb: could not connect to display` - Requires killing kwin_wayland via SSH and then SDDM appears - ~50% of cases: Only the memory leak occurs A potentially related issue was reported at https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12341#note_2657149, describing both freezing and memory leaks after sleep/wake cycles. While I am not sure to what extent the freezing behavior is related to the memory leak and everyone is discussing mostly the memory leak, I'm including this information since it was mentioned in the original bug description.
*** Bug 495991 has been marked as a duplicate of this bug. ***
(In reply to Lech from comment #35) > - are we all using optimus with the amd/intel GPU as the main one? In my case it's NVIDIA/Intel > - do we all have the external monitor ports connected to the same GPU? My monitor is connected to the HDMI port, I'm not sure which GPU this port is connected to, though. > - are we all having this issue only when putting the laptop to sleep and > waking it up? No, in my case it's reproducible even after a cold boot. I have a small update, not sure if it will be useful, but anyway... The built-in screen on my laptop has been having issues for the past couple of months, and a few days ago it finally died, so only the external display is working now. So, I went into the BIOS and completely disabled the built-in display. Now, only one display is shown in the system settings, and the issue is no longer reproducible.
I am also facing this issue. I had it literally crash my IDE and PPT software in the middle of my tasks due to the kernel OOM mechanism kicking in. The unique part compared to all others here is that I only have an Intel iGP in my system. No dGPs. The workarounds mentioned here of unplugging and replugging the HDMI cord unfortunately doesn't work for me, and neither does temporarily switching to a VTE do anything. I have had to do unsafe shutdowns or SysRq+B in order to get out of this situation and regain usefulness of my laptop. The worst part is that I've had to run fsck manually whenever I do this since the reboot would drop me in a shell, saying I have to manually run it. Thankfully, I have had no data loss yet. Here is my laptop's specs: [SPEC] Operating System: Arch Linux KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.13.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i7-1260P Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Iris® Xe Graphics Manufacturer: LENOVO Product Name: 21CDCTO1WW System Version: ThinkPad X1 Yoga Gen 7 ADDITIONAL INFORMATION At it's peak, I have had it occupy upto 15.2 GB, with the only reason me being able to save my work and force exit being that I allocated 10 GB for swap, which gave me just enough time to write everything to disk. I only use one external monitor.
I have the same issue with the memory leak described above. My steps to reproduce: 1. Turn on my laptop as usual 2. For some reason the external monitor is not sowing anything at all 3. Unplug the HDMI connector from the laptop, plug it in back. 4. kwin_wayland process starts slowly leaking memory. kwin_wayland leaks memory faster and faster after being in this state for some time. After eating up all the available RAM (31+ GiB) it gets killed by earlyoom killer. Restarting it with kwin_wayland --replace helps me as well. My system specs are: Operating System: Arch Linux KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.13.2-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Xe Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: Katana GF76 12UGS System Version: REV:1.0 $ inxi -G Graphics: Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] driver: i915 v: kernel Device-2: NVIDIA GA104 [Geforce RTX 3070 Ti Laptop GPU] driver: nvidia v: 570.86.16 Display: unspecified server: X.Org v: 24.1.5 with: Xwayland v: 24.1.5 driver: X: loaded: modesetting,nvidia dri: iris gpu: i915,nvidia,nvidia-nvswitch resolution: 1: 2560x1440~144Hz 2: 1920x1080~144Hz API: EGL v: 1.5 drivers: iris,nvidia platforms: gbm,x11,surfaceless,device API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: intel mesa v: 24.3.4-arch1.1 renderer: Mesa Intel Iris Xe Graphics (ADL GT2) API: Vulkan v: 1.4.303 drivers: N/A surfaces: xcb,xlib Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr $ pacman -Qi kwin Name : kwin Version : 6.2.5-3 ...
(In reply to Chan from comment #45) > I am also facing this issue. I had it literally crash my IDE and PPT > software in the middle of my tasks due to the kernel OOM mechanism kicking > in. The unique part compared to all others here is that I only have an Intel > iGP in my system. No dGPs. Until we know differently, I would assume that to be a different problem. Please make a separate bug report about that.
im unsure if what im experiencing is the same issue or not, but for me kwin_waylands memory usage gets increased by a lot by repeatedly fullscreening and unfullscreening a program, with each fullscreen the memory usage gets higher and higher with my desktop just getting more and more laggy and freezy and a full restart is needed to fix it, ive seen it go up to 8 gigs of ram before. this can get really annoying as i tend to watch youtube videos in fullscreen and i unfullscreen them multiple times to check up on messages, causing the freezes to kick in fast. Operating System: EndeavourOS KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.13.2-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-3770K CPU @ 3.50GHz Memory: 23,4 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 980
I brought this up on Matrix back when the 565 Nvidia driver update dropped, and it was suggested it could be a bug in the driver itself and not kwin, not sure if that's correct. I downgraded to 560 and never had these issues again, until I tried upgrading to 570 yesterday. The issues are back :/ The behaviour I'm observing matches exactly what kde.2ip0k@aihaiti.space described: after reconnecting a display (be it manually re-plugging or waking from sleep), the memory starts leaking pretty fast until it consumes everything. The rate at which it leaks seems somewhat related to the repainting frequency. Replacing kwin works, but is somewhat disrupting, of course, as not all windows are automatically recovered. Also requires me to restart plasmashell (otherwise it gets stuck in a weird, partially functioning state). Here's my system information: Operating System: Manjaro Linux KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.12.12-2-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 And also inxi -G: Graphics: Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] driver: i915 v: kernel Device-2: NVIDIA TU116M [GeForce GTX 1660 Ti Mobile] driver: N/A Display: wayland server: X.Org v: 24.1.4 with: Xwayland v: 24.1.4 compositor: kwin_wayland driver: X: loaded: modesetting unloaded: nvidia dri: iris gpu: i915 resolution: 1920x1080~144Hz API: EGL v: 1.5 drivers: iris,swrast platforms: gbm,wayland,x11,surfaceless,device API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.3.4-arch1.1 renderer: Mesa Intel UHD Graphics 630 (CFL GT2) API: Vulkan v: 1.4.303 drivers: N/A surfaces: xcb,xlib,wayland Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor gpu: gputop, intel_gpu_top, lsgpu, nvidia-settings, nvidia-smi wl: swaymsg,wayland-info x11: xdpyinfo, xprop, xrandr I'm not sure why the driver is showing as N/A there. I have the nvidia-open-dkms Manjaro/Arch package at version 570.86.16-2 (latest atm).
I experience the same thing. For me it stops at 11GB memory usage. If I unplug the monitor nothing happens, only when I plug it back whole Plasma restarts (closing all my apps) but then the memory usage rises much faster than it did in the first place. I have realised that it depends on the amount of pixels that have been changed since the start of the session, on a stable image it doesn't rise at all and on a video playback or when swinging a window around it rises. The leak doesn't happen at all when the iGPU is turned off in the bios. System: Arch Linux Kernel: 6.13.2-arch1-1 Plasma version: 6.3.0 Frameworks version: 6.10.0 Qt version: 6.8.2 Graphics platform: Wayland CPU: Intel Core i5 13500h iGPU: Intel Iris Xe Graphics dGPU: Nvidia RTX 4050 Mobile
So I bought an external monitor a few weeks ago and it's happening to me. I am on a AMD Laptop with an integrated nvidia card too. The monitor is plugged with a USB-C to DisplayPort cable, which has occasional disconnections. I am on Fedora 41 dnf info kwin Updating and loading repositories: Repositories loaded. Installed packages Name : kwin Epoch : 0 Version : 6.3.0 Release : 3.fc41 Architecture : x86_64 Installed size : 12.0 B Source : kwin-6.3.0-3.fc41.src.rpm From repository : updates Summary : KDE Window manager URL : https://userbase.kde.org/KWin License : BSD-2-Clause AND BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND GPL-3.0-or-later AND L : GPL-2.0-only AND LGPL-2.0-or-later AND LGPL-2.1-only AND LGPL-2.1-or-later AND LGPL-3.0-only AND (GPL-2.0-only OR GPL-3.0-o : nly) AND (LGPL-2.1-only OR LGPL-3.0-only) AND MIT Description : KDE Window manager. Vendor : Fedora Project inxi -G Graphics: Device-1: NVIDIA GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] driver: nvidia v: 565.77 Device-2: Advanced Micro Devices [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Mobile Series] driver: amdgpu v: kernel Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.5 compositor: kwin_wayland driver: gpu: amdgpu,nvidia,nvidia-nvswitch resolution: 1: 3440x1440~165Hz 2: 2560x1440~165Hz API: EGL v: 1.5 drivers: nvidia,radeonsi platforms: gbm,wayland,x11,surfaceless,device API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: amd mesa v: 24.3.4 renderer: AMD Radeon Graphics (radeonsi renoir LLVM 19.1.7 DRM 3.59 6.12.13-200.fc41.x86_64) API: Vulkan v: 1.4.304 drivers: N/A surfaces: xcb,xlib,wayland Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor gpu: nvidia-settings, nvidia-smi, radeontop wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr wayland-info | grep NVIDIA returns nothing but wayland-info | grep AMD returns something so it is most likely the main.
And I have this result: journalctl --user-unit plasma-kwin_wayland --boot 0 | grep import févr. 16 14:38:20 Cassini kwin_wayland[2651]: kwin_wayland_drm: chose egl import with format AB30 and modifier 0 févr. 16 14:38:20 Cassini kwin_wayland[2651]: kwin_wayland_drm: chose egl import with format AB4H and modifier 0
Hi same issue here > Trying to be helpful here: > - are we all using optimus with the amd/intel GPU as the main one? Intel integrated GPU (i9-13980HX CPU) with NVidia 4 4080 laptopDGPU. > - do we all have the external monitor ports connected to the same GPU? I think laptop screen is on iGPU. External monitor connected to dGPU by thunderbolt 4 > - are we all having this issue only when putting the laptop to sleep and > waking it up? No, It's all the time. I use a KVM to work and having to reconnect the cord (or changing KVM source and restoring to the laptop source) is a hell. I've realised that memory leaks increases considerably when playing RTSP streaming (sourveilance camera) on VLC. I dont know if happens to while playing other kind of media. My setup: bazzite-asus-nvidia-open:stable Bazzite 41 (FROM Fedora Kinoite) Linux 6.12.12-207.bazzite.fc41.x86_64 21 hours, 53 mins Spawned on Feb 22 2025 ROG Strix G614JZ_G614JZ (1.0) 13th Gen Intel(R) Core(TM) i9-13980HX (32) @ 5.60 GHz NVIDIA GeForce RTX 4080 Max-Q / Mobile [Discrete] Intel Raptor Lake-S UHD Graphics @ 1.65 GHz [Integrated] 11.70 GiB / 30.95 GiB (38%) 14.01 GiB / 114.00 GiB (12%) - btrfs [Read-only] 14.43 GiB / 115.50 GiB (12%) - btrfs 28.63 GiB / 399.96 GiB (7%) - btrfs 538.81 GiB / 1.82 TiB (29%) - btrfs 2560x1440 @ 120 Hz (as 2048x1152) in 27" [External] 50% [AC Connected] ASUSTeK ROG CHAKRAM X KDE Plasma 6.3.0 KWin (Wayland) bash 5.2.32 Ptyxis 47.6 2683 (rpm), 56 (flatpak), 27 (brew)
Hey there, same issue here. I have i5-13420H iGPU and RTX 4050 Laptop dGPU. External monitor is connected via HDMI/Thunderbolt, and is operated by dGPU. Issue occurs with or without sleep/hibernation. Other sysinfo: Operating System: Arch Linux KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.5-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × 13th Gen Intel® Core™ i5-13420H Memory: 15,3 GiB of RAM Graphics Processor 1: Mesa Intel® Graphics Graphics Processor 2: llvmpipe Manufacturer: LENOVO Product Name: 82XV System Version: LOQ 15IRH8
Same issue here. Laptop MSI GS75 Stealth 9SF lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] 01:00.0 VGA compatible controller: NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] (rev a1) Issue occurs with or without sleep/hibernation. No memory leak on X11 Other sysinfo: Operating System: Kubuntu 25.04 KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.12.0-16-generic #16-Ubuntu SMP PREEMPT_DYNAMIC Graphics Platform: Wayland Processors: 12 × i7-9750H CPU @ 2.60GHz Memory: 14 GiB of RAM Graphics Processor 1: Intel Graphics Processor 2: Nvidia Manufacturer: Micro-Star International Co., Ltd. Product Name: GS75 Stealth 9SF System Version: Ubuntu 25.04 Ubuntu Plucky Puffin (development branch)
I, too, am suffering from an increased memory usage from kwin to the point of OOM, with resident memory often being at the 1.5G mark. However, unlike most (all?) reporters here I do not have a multi-GPU setup, but rather just a regular single-GPU Intel TigerLake laptop. I am usually connected to an external monitor, but when I do, my settings are configured to turn the laptop screen off, so I wouldn't even call it "multi-monitor" per se. No idea if this is the same bug as others have reported here or an entirely separate one. This is with Debian trixie, KWin 6.3.0, Wayland, HiDPI external monitor (scaling factor 2). I can find my way around gdb and Valgrind, so if you have any tips on how to best debug this, I'd love to hear them!
*** Bug 497041 has been marked as a duplicate of this bug. ***
I'm still seeing this issue on 6.3.2 consistently. Archlinux: AMD onboard graphics + Nvidia 3070 laptop My current workaround involves unplugging and reconnecting the external monitor once in a while when my RAM maxes out. The workaround is intermittent, sometimes the whole system freezes up on disconnecting. I have tried the env var change described in https://bbs.archlinux.org/viewtopic.php?id=301440 to no avail
This looks to be at least partly caused by the sleep/wake functionality from my experience. Memory usage looks to be stable until the machine has gone through a sleep cycle. On wake when logging back into the desktop memory usage from the kwin_wayland process will steadily start to increase until an OOM causes the process to fully crash or monitors are disconnected and reconnected. From what I've seen this is also happening on machines with the following hardware set up: an internal GPU (intel/AMD) a dedicated GPU (Nvidia) plasma version: 6.3.2 Nvidia driver: 570.124.04
(In reply to Daniela Henkel from comment #48) > im unsure if what im experiencing is the same issue or not, but for me > kwin_waylands memory usage gets increased by a lot by repeatedly > fullscreening and unfullscreening a program, with each fullscreen the memory > usage gets higher and higher with my desktop just getting more and more > laggy and freezy and a full restart is needed to fix it, ive seen it go up > to 8 gigs of ram before. this can get really annoying as i tend to watch > youtube videos in fullscreen and i unfullscreen them multiple times to check > up on messages, causing the freezes to kick in fast. > > Operating System: EndeavourOS > KDE Plasma Version: 6.3.0 > KDE Frameworks Version: 6.10.0 > Qt Version: 6.8.2 > Kernel Version: 6.13.2-arch1-1 (64-bit) > Graphics Platform: Wayland > Processors: 8 × Intel® Core™ i7-3770K CPU @ 3.50GHz > Memory: 23,4 GiB of RAM > Graphics Processor: NVIDIA GeForce GTX 980 Same behaviour on my machine. I did some testing with mpv and noticed: pressing f to toggle fullscreen 16 times will guarantee a small leak. Once it has started to leak, it is guaranteed to leak again each time it leaves fullscreen. The same is true of f in VLC and Haruna, and F11 in Firefox, even on the new tab page. The 16th press is where the problem begins. There is a noticeable lag spike when the memory leaks, and again when closing the responsible program. Reboot or kwin_wayland --replace to remedy, but Firefox will close during either of these. RAM usage for mpv tests looked like this: 1.7GiB to start, with video open and playing in a small window. 16 fullscreen toggles later: the first permanent increase to 1.9GiB Subsequent fullscreen/unfullscreen cycles: 2.5, 4.8, 14.3 GiB Other runs: (kwin_wayland --replace) [1.7,(16 fullscreen toggles...) 1.8, 2.4, 4.8, 14.3] GiB (and after a reboot) [1.7,(16 fullscreen toggles...) 1.9, 2.5, 4.9, 14.4] GiB And so, with ~16GB RAM my PC crashed when leaving fullscreen on my 11th YouTube video of the session, with at most 2 tabs open in Firefox at any given time: one video, and one other tab to open new videos from. I toggled fullscreen during this session only by clicking the button at the bottom right of the video. Independent processes do not affect each other. mpv can be closed before leaking (even with alt+F4 to avoid the problematic 16th toggle), and opened again with the full 16 toggle grace. Using external video players to watch each YouTube video does escape Firefox's fullscreen limit, if otherwise less than ideal. I'd be very interested to hear if this magic number "16" (i.e. 8 times *leaving* fullscreen) is the same for anyone else. It's likely that I'll file a separate report in the morning regardless of feedback, but if anyone outside of EndeavourOS can't replicate, that would help get this to the right team. Operating System: EndeavourOS KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Desktop running identical dual monitors, one through a DisplayPort->HDMI adapter
(In reply to Faidon Liambotis from comment #56) > I, too, am suffering from an increased memory usage from kwin to the point > of OOM, with resident memory often being at the 1.5G mark. > > However, unlike most (all?) reporters here I do not have a multi-GPU setup, > but rather just a regular single-GPU Intel TigerLake laptop. I am usually > connected to an external monitor, but when I do, my settings are configured > to turn the laptop screen off, so I wouldn't even call it "multi-monitor" > per se. > > No idea if this is the same bug as others have reported here or an entirely > separate one. > > This is with Debian trixie, KWin 6.3.0, Wayland, HiDPI external monitor > (scaling factor 2). > > I can find my way around gdb and Valgrind, so if you have any tips on how to > best debug this, I'd love to hear them! Ok, so I am not the only one with just an iGPU facing this OOM situation.
Is anyone here facing this issue while running the 6.6 LTS kernel? I somehow don't face this problem when I am running the 6.6 LTS kernel. I have run the same setup (just the latest KDE 6.3.2 and Frameworks) for a week straight (no reboots) with an external monitor connected, just on the 6.6 LTS kernel, and didn't face an OOM. As such, I am now running the 6.6 LTS for the daily usage, and it's running normally with no issues. So maybe even though it's still kwin_wayland (or kwin_wayland_wrapper?) that eventually fills the memory to the point of OOM, but it's somehow an upstream kernel issue? Can someone else check this or is this a separate issue for me, and I am lucky it doesn't happen on 6.6 LTS?
(In reply to comment #48) (In reply to comment #60) I have upgraded my system today and this problem seems resolved. I have closed my separate report, I hope it's resolved for you too. Operating System: EndeavourOS KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.6-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series
I'm still having this issue in 6.3.3. Memory usage slowly rises over time and resets after unplugging and replugging the external screen (USB-C dock -> HDMI) or replacing kwin_wayland. With my system it chews through 10gb of RAM in ~3 or 4 hours. Operating System: openSUSE Tumbleweed 20250313 KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.6-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 5900HS with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor 1: AMD Radeon Graphics Graphics Processor 2: llvmpipe Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Zephyrus G15 GA503QR_GA503QR System Version: 1.0
*** Bug 500792 has been marked as a duplicate of this bug. ***
Still the same on 6.3.3 here :(
(In reply to Chan from comment #62) > Is anyone here facing this issue while running the 6.6 LTS kernel? I somehow > don't face this problem when I am running the 6.6 LTS kernel. I have run the > same setup (just the latest KDE 6.3.2 and Frameworks) for a week straight > (no reboots) with an external monitor connected, just on the 6.6 LTS kernel, > and didn't face an OOM. As such, I am now running the 6.6 LTS for the daily > usage, and it's running normally with no issues. So maybe even though it's > still kwin_wayland (or kwin_wayland_wrapper?) that eventually fills the > memory to the point of OOM, but it's somehow an upstream kernel issue? Can > someone else check this or is this a separate issue for me, and I am lucky > it doesn't happen on 6.6 LTS? Indeed this is likely a kernel issue anyone reported to amdgpu and nvidia-open?
I also have the same issue. I'm using Fedora 41 (KDE Spin) on an Acer Nitro 5 with a discrete NVIDIA GPU. I use it with the laptop lid closed and an external monitor plugged. This problem has been bugging me for a few weeks now, multiple times a day. I have a system with 32GB of RAM that gets completely taken by kwin_wayland after some time. The workaround of unplugging the HDMI cable and plugging again seems to work. After I plug the cable again the RAM usage drops by 10-15 GB at once. I noticed a lot of memory seems to be allocated by the NVIDIA driver somehow. I ran 'sudo pmap -x $(pidof kwin_wayland)' immediately before and after doing the workaround above. When I compared both outputs, there were many (> 5000) memory mappings labelled 'nvidiactl' that vanished after I plugged the cable back again. $ diff -W 200 --color=always -y ./kwin_wayland.pmap.before_unplug_plug.txt ./kwin_wayland.pmap.after_unplug_plug.txt | grep '<' | awk '{ print $6 }' | sort | uniq -c 5 [ 3 card0 1 card1 3 memfd:gdk-wayland 4 memfd:wayland-shm 5247 nvidiactl I'll be happy to provide more information about my system or run any more debugging commands to help diagnosing the problem if needed.
I can confirm I have the same issue. When I boot my laptop kwin_wayland process normally uses about 70MB of RAM and then over time while I use my laptop with my Samsung CRG9 49' external monitor the memory keeps growing until everything freezes.
For me the issue manifests a bit differently, so apologies if I should report this as a separate ticket instead. But it is instability involving multiple monitors in KDE 6. After turning monitors off and back on, either from power management settings or from manual power button push, sometimes video playback by any application (vlc, firefox, etc.) freezes the entire desktop for 30-60 seconds before updating the desktop once then freezing again until playback is paused/stops. Memory usage by kwin_wayland and plasmashell stay the same (about 400 MB and 600 MB respectively) during this time. kwin_wayland --replace does not help the issue, but pkill kwin_wayland and logging back in does. I did not experience the issue initially when I first installed Arch in January on I believe one of the last versions of KDE 5 to be shipped with it, and started noticing the issue some time after the upgrade to KDE 6. SYSTEM Arch running kernel 6.13.7-arch1-1 CPU: Ryzen 7 9700X GPU: AMD ATI Radeon RX 7900 XT Monitors: Sceptre M27 at 1920x1080@120Hz (non-primary); Gigabyte M28U at 3840x2160@144Hz (primary) $ pacman -Qi kwin Name : kwin Version : 6.3.3.1-1 STEPS TO REPRODUCE (for my specific hardware) Type 1: 1. Turn off primary display. Secondary display flashes, a device disconnect chime is heard, menubar on secondary display vanishes briefly. 2. Turn off secondary display. Device connect chime (from primary monitor) is heard. 3. Turn on secondary display. Disconnect and connect chime is heard. 4. Turn on primary display. Secondary display flashes, disconnect chime, menubar flicker, connect chime. 5. If unlucky, any video playback (vlc, firefox etc.) causes display freeze. Type 2: 1. Turn off primary display. Secondary display flashes, a device disconnect chime is heard, menubar on secondary display vanishes briefly, device connect chime is heard, menubar reappears with another minor flicker. 2. Turn on primary display. Secondary display flashes, disconnect chime, menubar flicker, connect chime, etc. 3. If unlucky, any video playback (vlc, firefox etc.) causes display freeze. LOG INFO In being able to force the type 2 scenario above from repeated power toggling, this is what was output to journalctl from primary display poweroff through the video playback freeze: Mar 23 10:27:09 Menphina org_kde_powerdevil[74224]: [ 81069] Removing connected display on bus 8 Mar 23 10:27:09 Menphina org_kde_powerdevil[74224]: [ 81069] Emitting DDCA_Display_Status_Event[939.372: DDCA_EVENT_DISPLAY_DISCONNECTED, card1-DP-1, dref: DDCA_Display_Ref[14], io_path:/dev/i2c-8, ddc working: false] Mar 23 10:27:09 Menphina org_kde_powerdevil[74224]: [ 81069] libddcutil callback thread 0x7926a401f770 started Mar 23 10:27:09 Menphina org_kde_powerdevil[74224]: [ 81069] Started 1 event callback thread(s) Mar 23 10:27:11 Menphina org_kde_powerdevil[74224]: [ 81069] Adding connected display with bus 8 Mar 23 10:27:11 Menphina org_kde_powerdevil[74224]: [ 81069] Emitting DDCA_Display_Status_Event[941.095: DDCA_EVENT_DISPLAY_CONNECTED, card1-DP-1, dref: DDCA_Display_Ref[15], io_path:/dev/i2c-8, ddc working: true] Mar 23 10:27:11 Menphina org_kde_powerdevil[74224]: [ 81069] libddcutil callback thread 0x7926a401a430 started Mar 23 10:27:11 Menphina org_kde_powerdevil[74224]: [ 81069] Started 1 event callback thread(s) Mar 23 10:27:11 Menphina org_kde_powerdevil[74224]: [ 74224] Quiescing libddcutil API... Mar 23 10:27:11 Menphina org_kde_powerdevil[74224]: [ 74224] Quiesce libddcutil API complete Mar 23 10:27:11 Menphina org_kde_powerdevil[74224]: [ 74224] Display redetection starting. Mar 23 10:27:11 Menphina org_kde_powerdevil[74224]: [ 81068] recheck thread terminating because watch thread terminated Mar 23 10:27:11 Menphina org_kde_powerdevil[74224]: [ 74224] Watch thread terminated. Mar 23 10:27:12 Menphina org_kde_powerdevil[74224]: [ 74224] Watching for display connection changes, resolved watch mode = Watch_Mode_Xevent, poll loop interval = 100 millisec Mar 23 10:27:12 Menphina org_kde_powerdevil[74224]: [ 74224] extra_stabilization_millisec: 0, stabilization_poll_millisec: 100 Mar 23 10:27:12 Menphina org_kde_powerdevil[74224]: [ 74224] libddcutil recheck thread (nil) started Mar 23 10:27:12 Menphina org_kde_powerdevil[74224]: [ 74224] libddcutil watch thread 0x600a3af462d0 started Mar 23 10:27:12 Menphina org_kde_powerdevil[74224]: [ 74224] Display redetection finished. Mar 23 10:27:12 Menphina org_kde_powerdevil[74224]: [ 74224] Unquiescing libddcutil API... Mar 23 10:27:12 Menphina org_kde_powerdevil[74224]: [ 81375] (dw_recheck_displays_func) Recheck interval: Slept for 200 millisec Mar 23 10:27:16 Menphina org_kde_powerdevil[74224]: [ 81376] Removing connected display on bus 8 Mar 23 10:27:16 Menphina org_kde_powerdevil[74224]: [ 81376] Emitting DDCA_Display_Status_Event[945.787: DDCA_EVENT_DISPLAY_DISCONNECTED, card1-DP-1, dref: DDCA_Display_Ref[17], io_path:/dev/i2c-8, ddc working: false] Mar 23 10:27:16 Menphina org_kde_powerdevil[74224]: [ 81376] libddcutil callback thread 0x7926a0014860 started Mar 23 10:27:16 Menphina org_kde_powerdevil[74224]: [ 81376] Started 1 event callback thread(s) Mar 23 10:27:17 Menphina org_kde_powerdevil[74224]: [ 81376] Adding connected display with bus 8 Mar 23 10:27:18 Menphina org_kde_powerdevil[74224]: [ 81376] Emitting DDCA_Display_Status_Event[947.662: DDCA_EVENT_DISPLAY_CONNECTED, card1-DP-1, dref: DDCA_Display_Ref[18], io_path:/dev/i2c-8, ddc working: true] Mar 23 10:27:18 Menphina org_kde_powerdevil[74224]: [ 81376] libddcutil callback thread 0x7926a00062a0 started Mar 23 10:27:18 Menphina org_kde_powerdevil[74224]: [ 81376] Started 1 event callback thread(s) Mar 23 10:27:18 Menphina org_kde_powerdevil[74224]: [ 74224] Quiescing libddcutil API... Mar 23 10:27:21 Menphina org_kde_powerdevil[74224]: Error queiscing libdducitl API. 1 active API calls outstanding. Mar 23 10:27:21 Menphina org_kde_powerdevil[74224]: [ 74224] Error queiscing libdducitl API. 1 active API calls outstanding. Mar 23 10:27:21 Menphina org_kde_powerdevil[74224]: org.kde.powerdevil: [DDCutilDisplay]: ddca_close_display -3032 Mar 23 10:27:21 Menphina org_kde_powerdevil[74224]: library quiesced, ddca_close_display temporarily unavailable Mar 23 10:27:21 Menphina org_kde_powerdevil[74224]: [ 74224] Display redetection starting. Mar 23 10:27:21 Menphina org_kde_powerdevil[74224]: [ 81375] recheck thread terminating because watch thread terminated Mar 23 10:27:21 Menphina org_kde_powerdevil[74224]: [ 74224] Watch thread terminated. Mar 23 10:27:21 Menphina org_kde_powerdevil[74224]: [ 74224] Attempting to unlock display lock owned by different thread Mar 23 10:27:21 Menphina org_kde_powerdevil[74224]: [ 74224] Unexpected error DDCRC_LOCKED from unlock_display_by_dpath(Display_Path[/dev/i2c-6]) Mar 23 10:27:52 Menphina kwin_wayland[73944]: kwin_wayland_drm: The main thread was hanging temporarily! Most times I experience the issue nothing much is emitted to journalctl.
I have noticed something weird about this bug. After unplugging and plugging my monitors back in, kwin only happens to leak memory (for me) when moving the mouse on a monitor directly connected to the nvidia gpu, and it also comes with momentary cpu usage spikes (to 20-30% usage from a normal 5%).
(In reply to LucasGGamerM from comment #71) > I have noticed something weird about this bug. After unplugging and plugging > my monitors back in, kwin only happens to leak memory (for me) when moving > the mouse on a monitor directly connected to the nvidia gpu, and it also > comes with momentary cpu usage spikes (to 20-30% usage from a normal 5%). I did some more testing, and it appears to happen movement happens on the monitors connected to the nvidia gpu, not just mouse movements.
Any updates on this issue? Maybe any workaround? Kinda bad that i need to unplug my monitor 3-6 times a day. If any info is needed to understand problems cause, provide me guide how to get this requiered info, so i can provide it to you. Thanks!
(In reply to Vlad Zabotinsky from comment #73) > Any updates on this issue? Maybe any workaround? Kinda bad that i need to > unplug my monitor 3-6 times a day. If any info is needed to understand > problems cause, provide me guide how to get this requiered info, so i can > provide it to you. Thanks! Just do kwin_wayland --replace everytime you encounter this issue. It's not great and keep in mind most of your applications will be closed, but at least the memory leak won't happen until the next time you unplug and replug your monitor.
(In reply to righn from comment #74) > (In reply to Vlad Zabotinsky from comment #73) > > Any updates on this issue? Maybe any workaround? Kinda bad that i need to > > unplug my monitor 3-6 times a day. If any info is needed to understand > > problems cause, provide me guide how to get this requiered info, so i can > > provide it to you. Thanks! > > Just do kwin_wayland --replace everytime you encounter this issue. It's not > great and keep in mind most of your applications will be closed, but at > least the memory leak won't happen until the next time you unplug and replug > your monitor. Difficult to call it a workaround, if you have to close and reopen your apps several times per day (happens, if you walk with your laptop or put it to sleep, connecting and disconnecting it from external monitors).
the issue seems gone with Linux 6.14 from Archlinux core-testing. `kwin_wayland` RSS around 800mb, with 2 screens connected to the AMD iGPU and 1 to a NVIDIA 4060ti
the problem seems gone with Linux 6.14 from Archlinux core-testing. kwin_wayland RSS stable ~800mb, with 2 4k screens connected to AMD iGPU and 1 4k screen to NVIDIA 4060ti
Created attachment 179739 [details] signature.asc Promising... Which nvidia driver version are you on?
> Created attachment 179739 [details] > signature.asc Oops, forgot you shouldn't reply with signed emails on bugzilla...
(In reply to righn from comment #74) > (In reply to Vlad Zabotinsky from comment #73) > > Any updates on this issue? Maybe any workaround? Kinda bad that i need to > > unplug my monitor 3-6 times a day. If any info is needed to understand > > problems cause, provide me guide how to get this requiered info, so i can > > provide it to you. Thanks! > > Just do kwin_wayland --replace everytime you encounter this issue. It's not > great and keep in mind most of your applications will be closed, but at > least the memory leak won't happen until the next time you unplug and replug > your monitor. Unfortunately this isn't good workaround for me, because i have more than 10 windows of different apps opened simultaneously. To open them 6 times a day is out of question. (I have laptop, so unplug monitor is much faster). (In reply to tmpod from comment #78) > Created attachment 179739 [details] > signature.asc > > Promising... Which nvidia driver version are you on? Driver Version: 570.124.04 Kernel: 6.13.6-1-default Installed it from Nvidia .run file in OpenSuse TW.
I was replying to Bráulio, but more info is always good :)
After a bit of testing, it seems that in this report there are many separate issues, with similar symptoms - memory leak. Some people report that replugging the monitors temporarily resolves the issue, but I cannot confirm this; for me the only way that the issue can be resolved is to simply reboot. Also there is a discussion about kernel versions and in the thread there was mentioned that downgrading to 6.6 LTS fixes the issue, however again I cannot confirm this (maybe anybody else can?). I've not managed to test out the 6.14 kernel to try out if it resolves. May I suggest to create some kind of "checklist" from all the information in this issue to better group people with the same actual problem and symptoms, and from there we can create separate reports and focus more on the individual problems and their origin (as well as if the source is kwin, kernel etc.)? Is there anyone from the dev team/community who would be able to create such checklist?
Hi I'm having this issue as well. I'm adding a comment as another temporary workaround is to log out / log back in. Hope this helps someone. Still, here's some system info, just in case.: Operating System: Arch Linux KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 Kernel Version: 6.13.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7735HS with Radeon Graphics Memory: 14.9 GiB of RAM Graphics Processor 1: AMD Radeon 680M Graphics Processor 2: NVIDIA Corporation AD107M System Version: 1.0 Cheers :)
For me it was like the shr mem was increasing every second a couple of MB, when the content of the screen changed. So lets say you are on the browser scrolling this thread, and with every htop refresh, the memory increased. I was trying to get some insights stracing kwin_wayland, as it was anoying me quite often, but it seems i couldn't reproduce anymore after updating today.. My idea was to try soemthing like sudo strace -Ttvff -o strace_log -e trace=mmap,munmap,mremap -k -p $(pidof kwin_wayland) but Im not sure either it would be of help... For nowwith new version installed it ram is steady on 262MB of SHR 402M of Res. Nevermind... connecting / disconnecting the screen started raising the memory once again, but if you stop scrolling, it sometimes frees some memory... I'll try to gather the strace and see if it is of worth... (after a couple of mintues of writing and scroll here, 633M) My Specs pacman -Qi kwin Nombre : kwin Versión : 6.3.3.1-1 Descripción : An easy to use, but flexible, composited Window Manager Arquitectura : x86_64 NAME="EndeavourOS" BUILD_ID="2024.09.22" Operating System: KDE Plasma Version: 6.3.3 Qt Version: 6.8.2-3 Kernel Version: 6.12.20-1-lts Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 7940HS w/ Radeon 780M Graphics Memory: 30 GiB of RAM Graphics Processor: AMD Radeon 780M inxi -G Graphics: Device-1: NVIDIA AD106M [GeForce RTX 4070 Max-Q / Mobile] driver: nvidia v: 570.133.07 Device-2: Advanced Micro Devices [AMD/ATI] Phoenix1 driver: amdgpu v: kernel Device-3: Sonix USB2.0 HD UVC WebCam driver: uvcvideo type: USB Device-4: USB C Video Adaptor driver: N/A type: USB Display: wayland server: X.Org v: 24.1.6 with: Xwayland v: 24.1.6 compositor: kwin_wayland driver: X: loaded: amdgpu,nvidia unloaded: modesetting dri: radeonsi gpu: amdgpu,nvidia,nvidia-nvswitch resolution: 1: 2400x1350~100Hz 2: 1920x1080~144Hz API: EGL v: 1.5 drivers: kms_swrast,nvidia,radeonsi platforms: gbm,wayland,x11,surfaceless,device API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: amd mesa v: 25.0.2-arch1.2 renderer: AMD Radeon 780M (radeonsi phoenix LLVM 19.1.7 DRM 3.61 6.12.20-1-lts) API: Vulkan v: 1.4.309 drivers: N/A surfaces: xcb,xlib,wayland Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console, kscreen-doctor, xfce4-display-settings gpu: nvidia-smi wl: nwg-displays, swaymsg, wayland-info x11: xdpyinfo, xprop, xrandr