SUMMARY Plasmashell's memory use grows constantly by about 1M per second. (kglobalacceld also grows, but much slower) for my first login after a reboot. After testing by disabling auto-login and rebooting, I have shown that this problem *only* occurs when the first session was automatically logged in. So it seems probable it has something to do with the auto-login process. STEPS TO REPRODUCE 1. Configure my user to auto-log in by editing /etc/sddm.conf.d/kde_settings.conf to have the following stanza: [Autologin] Relogin=false Session=plasma User=tony 2. Reboot. OBSERVED RESULT Plasmashell leaks memory. EXPECTED RESULT Plasmashell doesn't leak memory. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro stable, fully updated. KDE Plasma Version: 6.0.5-1 KDE Frameworks Version: 24.05.2-1 (I think - not entirely certain) Qt Version: 6.7.2-1 ADDITIONAL INFORMATION This is new behaviour since Plasma 6 (earlier Plasmas 6 versions also exhibited it, but I didn't think to raise a bug).
It would be great if you can see if this is still a problem in Plasma 6.1 or even the 6.2 beta (6.2 is going to be released in a little over two weeks). 6.0 is rather old at this point.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
I've finally been able to install Plasma 6.1.5 and the problem still persists. However... I have experimented with a new user login configured as the auto-login user and the problem disappears. So it's evident the problem is somewhere in my (extensive) autostart setup, or something on my desktop configuration. So I'm closing this but as invalid.
A note for the benefit of anyone who finds this when looking for the solution to a similar problem. It was caused entirely by having Firefox launched from within an autostart script. Inhibiting Firefox for the first login of a newly-booted machine solves the problem. I have absolutely NO idea why.