Memory leak in `cosmic-settings`

[andre4ik3]

After exiting from COSMIC, there were still 3 instances of cosmic-settings left running (from me opening & closing it from within COSMIC), then while I was in KDE Plasma, the cosmic-settings instances were leaking memory in the background, and two were killed by the kernel OOM killer: Kernel OOM logs. The third one I recorded on video, it went up to around 94 GiB and then hovered there. However it would not respond to quit requests, I had to send a SIGKILL for it to close, even after it stopped growing in memory usage.

cosmic-settings.mp4

After I killed it, it sent this in journal:

app-cosmic-com.system76.CosmicAppList-344252.scope: Consumed 7min 19.390s CPU time, 94.1G memory peak.

OS: latest NixOS unstable, using latest nixos-cosmic flake
Version: cosmic-settings-1.0.0-alpha.4-unstable-2024-12-17

[bhh32]

Do you have any steps for us to try and replicate the issue? If we can get it to happen again, it may be easier for us to track down where in the code this is stemming from and fix it.

[andre4ik3]

I was able to reproduce it just now again on latest 2025.01.02 version. Each cosmic-setting process is using ~25 GiB, for a total of ~100 GiB.

1. Go to COSMIC (my display-manager is SDDM, not sure if it's relevant)
2. Open cosmic-settings, go to "Monitors" section
3. If you want, close and open a few times, it will reopen on "Monitors" section (in my screenshots I closed and reopened 4 times)
4. Exit COSMIC desktop
5. Enter KDE plasma, open system monitor and watch RAM go up (goes up faster the more times you opened/closed cosmic-settings)
6. (Optional) Kill all the cosmic-settings processes quickly before the system OOM's :)

[bhh32]

I was able to reproduce it just now again on latest 2025.01.02 version. Each cosmic-setting process is using ~25 GiB, for a total of ~100 GiB.

1. Go to COSMIC (my display-manager is SDDM, not sure if it's relevant)

2. Open cosmic-settings, go to "Monitors" section

3. If you want, close and open a few times, it will reopen on "Monitors" section (in my screenshots I closed and reopened 4 times)

4. Exit COSMIC desktop

5. Enter KDE plasma, open system monitor and watch RAM go up (goes up faster the more times you opened/closed cosmic-settings)

6. (Optional) Kill all the cosmic-settings processes quickly before the system OOM's :)

When you switched from COSMIC to KDE, did you log out and then back in? If not, how are you switching DEs?

It could be related to you running SSDM, but I don't know that for sure. Is there a way for you to check if this happens when you're running cosmic-comp instead of SSDM?

[andre4ik3]

When you switched from COSMIC to KDE, did you log out and then back in? If not, how are you switching DEs?

Yes, I logged out from COSMIC, switched the session in SDDM from COSMIC to Plasma (Wayland), then logged back in.

It could be related to you running SSDM, but I don't know that for sure. Is there a way for you to check if this happens when you're running cosmic-comp instead of SSDM?

Just checked by doing services.displayManager.cosmic-greeter.enable = true;, and following the steps outlined above, the issue remains. I opened and closed cosmic-settings 3 times, and there was 3 cosmic-settings leaking memory after logging out from COSMIC and logging into KDE.

[bhh32]

When you switched from COSMIC to KDE, did you log out and then back in? If not, how are you switching DEs?

Yes, I logged out from COSMIC, switched the session in SDDM from COSMIC to Plasma (Wayland), then logged back in.

It could be related to you running SSDM, but I don't know that for sure. Is there a way for you to check if this happens when you're running cosmic-comp instead of SSDM?

Just checked by doing services.displayManager.cosmic-greeter.enable = true;, and following the steps outlined above, the issue remains. I opened and closed cosmic-settings 3 times, and there was 3 cosmic-settings leaking memory after logging out from COSMIC and logging into KDE.

Ok, thanks for checking and giving all the information.

[aurabindo]

Also seeing a memleak. I'm on Cachy OS, and also have rusty userspace scheduler in use.
Dmesg: https://pastebin.com/k7b9jN4b

I was changing changing some keyboard shortcuts, and changing various fonts when I noticed the hang.

[MalcolmReed-ent]

Hey guys, I discovered a memory leak while running Alpha 5 on Arch Linux. I encountered it through two different scenarios: first while adjusting display settings (though I didn't track the exact steps), and second by running cosmic-settings, logging out, and then launching settings again, the second occurrence was the one I gathered info from.

I ran various versions of valgrind here is the first

valgrind --leak-check=full --show-leak-kinds=all --track-origins=yes --verbose --log-file=cosmic-settings-valgrind.log cosmic-settings

and the second was

valgrind --tool=massif cosmic-settings 2> cosmic-settings-memory-profile.log

and here are the various files i have accumulated from it

massif.out.172478.log

cosmic-settings-memory-profile.log

cosmic-settings-valgrind.log

[bhh32]

So it seems the 3 examples we currently have of this are all coming from non-Pop!_OS distros. Would that be correct? I need to do some more testing on Pop!_OS to see if this is something that can be traced to outside distros.

It looks like 2 Arch based distros and one unstable NixOS install.

Can you all confirm your kernel versions for me?

Also, just to confirm, where are the packages coming from on the Arch-based distros having this issue?

[bhh32]

Also seeing a memleak. I'm on Cachy OS, and also have rusty userspace scheduler in use.

Dmesg: https://pastebin.com/k7b9jN4b

I was changing changing some keyboard shortcuts, and changing various fonts when I noticed the hang.

Do you also have KDE installed? I see references to SSDM in your paste bin.

[bhh32]

Hey guys, I discovered a memory leak while running Alpha 5 on Arch Linux. I encountered it through two different scenarios: first while adjusting display settings (though I didn't track the exact steps), and second by running cosmic-settings, logging out, and then launching settings again, the second occurrence was the one I gathered info from.

I ran various versions of valgrind here is the first

valgrind --leak-check=full --show-leak-kinds=all --track-origins=yes --verbose --log-file=cosmic-settings-valgrind.log cosmic-settings

and the second was

valgrind --tool=massif cosmic-settings 2> cosmic-settings-memory-profile.log

and here are the various files i have accumulated from it

massif.out.172478.log

cosmic-settings-memory-profile.log

cosmic-settings-valgrind.log

Do you also have KDE and/or SSDM installed?

[MalcolmReed-ent]

Hey guys, I discovered a memory leak while running Alpha 5 on Arch Linux. I encountered it through two different scenarios: first while adjusting display settings (though I didn't track the exact steps), and second by running cosmic-settings, logging out, and then launching settings again, the second occurrence was the one I gathered info from.
I ran various versions of valgrind here is the first
valgrind --leak-check=full --show-leak-kinds=all --track-origins=yes --verbose --log-file=cosmic-settings-valgrind.log cosmic-settings
and the second was
valgrind --tool=massif cosmic-settings 2> cosmic-settings-memory-profile.log
and here are the various files i have accumulated from it
massif.out.172478.log
cosmic-settings-memory-profile.log
cosmic-settings-valgrind.log

Do you also have KDE and/or SSDM installed?

No, just cosmic, I removed all of KDE and QT hours before running just cosmic, I was using all of cosmic-session with optional dependencies installed, when I logged out, I signed back in with cosmic-greeter

I installed the cosmic session from the Arch extra repository
https://archlinux.org/packages/extra/x86_64/cosmic-session/

As for my setup here is my fastfetch
OS: Arch Linux x86_64
Host: OptiPlex 9020 (00)
Kernel: Linux 6.12.9-arch1-1
Uptime: 5 mins
Packages: 597 (pacman)
Shell: bash 5.2.37
Display (DELL P2017H): 1600x900 @ 60 Hz in 19" [External]
WM: cosmic-comp (Wayland)
Theme: Breeze [GTK2]
Icons: breeze [GTK2]
Font: Noto Sans (10pt) [GTK2]
Cursor: breeze (24px)
Terminal: cosmic-term
CPU: Intel(R) Core(TM) i7-4790 (8) @ 4.00 GHz
GPU 1: AMD Radeon RX 550 / 550 Series [Discrete]
GPU 2: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller @ 1.20 GHz [Integrated]
Memory: 2.51 GiB / 31.25 GiB (8%)
Swap: 0 B / 4.00 GiB (0%)
Disk (/): 244.84 GiB / 952.87 GiB (26%) - btrfs
Locale: en_US.UTF-8

[mmstick]

Make sure you have the latest version of cosmic-settings from git. Arch Linux users can use the Chaotic AUR. Font caching issues were resolved last week, as well as a bounded channel on the display settings page blocking the app from exiting.

[mmstick]

See 7576ad1