Created attachment 141828 [details] htop SUMMARY: Plasmashell is using too much RAM. It always shows ram usage in range (600,950). Usage stays persistent from boot to shutdown. Might be a memory leak. STEPS TO REPRODUCE 1. I used htop and cat /proc/meminfo arrived at conclusion that plasmashell is the culprit and it also renders my laptop unreliable as it becomes laggy. 2. No idea if it is even reproducible. 3. OBSERVED RESULT https://ibb.co/m06jzk1 EXPECTED RESULT Already briefed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.6-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7 CPU M 620 @ 2.67GHz Memory: 3.7 GiB of RAM Graphics Processor: NVA8
Your screenshot appears to show firefox using 4 GB of RAM, but I can't see plasmashell in there. What are you doing when the memory climbs? How long has the plasmashell process been running for? Do you notice that it leaks memory with every notification? If you disable receiving notifications by enabling Do Not Disturb mode, does the memory leak go away?
Thanks for the lightening reply. I really appreciate it ! In some thread online, I read that clearing the cache resolved some similar problem so I did do that and after a reboot the exaggerated memory usage decreased to around 7%. Also I changed the compositor settings from openGL 3.1 to openGL 2.0 , Is around 7% alright for plasmashell? 1.Sorry for the useless screenshot, I must have been sleepy when i took it. When I hovered the mouse pointer over the taskbar so as for taskbar preview, the ram usage used to increase. More than one tab of dolphin file explorer was enough to spike the usage by 5~6 percent. It all happened cumulatively. As I mentioned the graph flattened nearly around 22%. 2.When the system booted, the process plasma shell consumed nearly around 3% and with it kept on increasing until the 22-23% maxima. 3.Yes the notifications did sway the memory but so did everything following the few minutes of booting of system. It used to become so snappy that the computer was barely usable.
*** This bug has been marked as a duplicate of bug 442844 ***