Bug 501366

Summary: System Settings takes 800+ MB of memory
Product: [Applications] systemsettings Reporter: Riccardo Robecchi <sephiroth_pk>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: john.kizer, kde, kdedev, nate, sitter
Priority: NOR    
Version First Reported In: 6.3.2   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Screenshot

Description Riccardo Robecchi 2025-03-11 15:41:57 UTC
Created attachment 179310 [details]
Screenshot

SUMMARY
System Settings appears to have a memory leak somewhere, as I found it taking more than 800 MB of memory. This happened while displaying the audio settings, but the application had been opened for a few hours, during which I used various pages (KWin, theme, display, audio...).

STEPS TO REPRODUCE
1. Open System Settings
2. ?

OBSERVED RESULT
System Settings takes a lot of RAM.

EXPECTED RESULT
System Settings keeps RAM usage low and constant.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2025-03-11 23:48:08 UTC
This is on X11, I assume? Do you by any chance have any 3rd-party KCMs installed?
Comment 2 Riccardo Robecchi 2025-03-12 09:13:06 UTC
Yes, this is on X11. AFAIK I don't have any 3rd-party KCMs installed.
Comment 3 Harald Sitter 2025-03-12 13:34:45 UTC
I am not sure we'll be able to do anything here unless you can narrow down when the leak appears.
Comment 4 John Kizer 2025-03-26 17:33:23 UTC
Hi - are you able to watch the memory consumption as you use the app, and identify specifically when usage spikes?
Comment 5 Riccardo Robecchi 2025-03-28 14:53:07 UTC
I have tried to replicate the behaviour, but failed so far. I have been able to make memory consumption grow to 400+ MB, however, just by visiting different KCMs.
Comment 6 David Edmundson 2025-10-23 15:10:24 UTC
Anything large that doesn't happen for everyone is almost always graphics memory which often get fixed by 3rd party changes.

Can you confirm if this is still an issue?
Comment 7 Riccardo Robecchi 2025-10-29 16:22:08 UTC
I can confirm I haven't seen this again. Thanks to everyone for their work.