Created attachment 156615 [details] heaptrack of plasmashell exhibiting the issue SUMMARY Something, not sure what, causes plasmashell to consume 1.3 GB of memory. Additionally, new programs can no longer be launched from the application launcher, showing the error "Resource error (fork failure): Cannot allocate memory" With the dmesg output: [ 1827.216162] __vm_enough_memory: pid: 3772, comm: plasmashell, no enough memory for the allocation This was not an issue in plasma 5.26, and started happening with 5.27.0 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.1.12 (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Heaptrack shows huge RSS size, but no specific allocation that caused the heap to grow so large.
Do you have external monitors? Do you have an NVIDIA GPU? Do you use the nvidia-settings app to turn on or off monitors?
No external monitors, AMD integrated GPU (Vega 8).
Thanks for the info.
Here's another heaptrack that was captured from the moment plasmashell started, where it exhibits the same issue pretty much immediately. I don't know how to interpret the output, it doesn't *seem* to be tracking the actual problematic allocations, hinting at something more sinister: https://overviewer.org/~pillow/up/6c583e01f5/heaptrack.plasmashell.65921.zst As an aside node, my current plasmashell process is consuming 2 GiB of memory right now and also doesn't allow me to launch applications through the menu. It seems to get worse over time
I did some more testing. plasmashell enters its broken memory-hogging non-application-launching state the moment I search for "k" in the application launcher. This happens with *all* search plugins disabled, i.e. no results being returned.
Does KRunner also begin to consume excessive memory when you use KRunner to search for "k"?
(In reply to Nate Graham from comment #6) > Does KRunner also begin to consume excessive memory when you use KRunner to > search for "k"? No, KRunner continues to work as normal and does not consume excessive amounts of memory.
*** This bug has been marked as a duplicate of bug 465705 ***
Don't think that's the same bug, removing the ScreenMapping section from my appletsrc and restarting plasmashell does not resolve the issue.
Ok, thanks.
This is still an issue in 5.27.6. Is there any additional info I can provide to help narrow this down? Another machine using the same plasma version doesn't have this issue, so I assume it's either some configuration or hardware causing this.
Many things have changed under the hood in the past year. Can I ask you to report whether this is still reproducible in any capacity in Plasma 6.1.4 or later?
Hasn't happened since the switch to Plasma 6 for me.