Bug 501366 - System Settings takes 800+ MB of memory
Summary: System Settings takes 800+ MB of memory
Status: REPORTED
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 6.3.2
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-11 15:41 UTC by Riccardo Robecchi
Modified: 2025-03-28 14:53 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Screenshot (66.98 KB, image/png)
2025-03-11 15:41 UTC, Riccardo Robecchi 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
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.