Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible memory leak #442

Open
ChildishGiant opened this issue Mar 17, 2022 · 3 comments
Open

Possible memory leak #442

ChildishGiant opened this issue Mar 17, 2022 · 3 comments

Comments

@ChildishGiant
Copy link

ChildishGiant commented Mar 17, 2022

What Happened?

My system was having hitches so I opened up monitor and saw wingpanel was using 2GB of ram. I restarted it and now it's only using 96MB. This was after around 12 hours of uptime, with a few sleeps.

Steps to Reproduce

No clue, sorry

Expected Behavior

Wingpanel probably shouldn't be using half the total recommended ram

OS Version

6.x (Odin)

Software Version

Latest release (I have run all updates)

Log Output

No response

Hardware Info

         eeeeeeeeeeeeeeeee            allie@elementary-os-desktop
      eeeeeeeeeeeeeeeeeeeeeee         ------------------------------------ 
    eeeee  eeeeeeeeeeee   eeeee       OS: elementary OS 6.1 Jólnir x86_64 
  eeee   eeeee       eee     eeee     Kernel: 5.16.10-051610-generic 
 eeee   eeee          eee     eeee    Uptime: 13 hours, 52 mins 
eee    eee            eee       eee   Packages: 2811 (dpkg), 138 (flatpak), 10 (snap) 
eee   eee            eee        eee   Shell: bash 5.0.17 
ee    eee           eeee       eeee   Resolution: 1920x1080, 1920x1080 
ee    eee         eeeee      eeeeee   DE: Pantheon 
ee    eee       eeeee      eeeee ee   WM: Mutter(Gala) 
eee   eeee   eeeeee      eeeee  eee   Terminal: io.elementary.t 
eee    eeeeeeeeee     eeeeee    eee   CPU: AMD Ryzen 5 1600X (12) @ 3.600GHz 
 eeeeeeeeeeeeeeeeeeeeeeee    eeeee    GPU: AMD ATI Radeon RX 470/480/570/570X/580/580X/590 
  eeeeeeee eeeeeeeeeeee      eeee     Memory: 6664MiB / 15995MiB 
    eeeee                 eeeee
      eeeeeee         eeeeeee                                 
         eeeeeeeeeeeeeeeee                                    
@jeremypw
Copy link
Collaborator

Do you have a large number of notifications? There are known issues around handling those. If each notification object is not being properly destroyed then it could explain the memory leak. That is a lot of memory to leak though!

This was referenced Apr 15, 2023
@peteruithoven
Copy link
Collaborator

More info on the notifications issue:
elementary/wingpanel-indicator-notifications#237
elementary/wingpanel-indicator-notifications#241
What happens when you clear your notifications list?

We've had an issue with incredibly large icons in the applications menu in the past. elementary/applications-menu#117 (comment)

Maybe try keeping an eye on it's memory usage, restarting wingpanel and opening the applications menu, going through it's pages, using other indicators, just trying actions you might take normally. See if anything triggers the memory usage.

@pietpaff
Copy link

pietpaff commented Nov 28, 2023

I'm getting similar behaviour now on Horus. Wingpanel hogs 25% (1 of 4 threads) of the CPU and floads the RAM reaching up to 2GB after a while without me even interacting with it.

I killed wingpanel and manually restarted it in the terminal to maybe see any errors and it reports some critical.

(io.elementary.wingpanel:4710): nm-CRITICAL **: 00:27:32.905: ((src/libnm-client-impl/nm-device.c:1141)): assertion '' failed
(io.elementary.wingpanel:4710): nm-CRITICAL **: 00:27:32.905: ((src/libnm-client-impl/nm-device.c:1141)): assertion '' failed
(io.elementary.wingpanel:4710): nm-CRITICAL **: 00:27:32.905: ((src/libnm-client-impl/nm-device.c:1141)): assertion '' failed
(io.elementary.wingpanel:4710): nm-CRITICAL **: 00:27:32.905: ((src/libnm-client-impl/nm-device.c:1141)): assertion '' failed
(io.elementary.wingpanel:4710): nm-CRITICAL **: 00:27:32.905: ((src/libnm-client-impl/nm-device.c:1141)): assertion '' failed
(io.elementary.wingpanel:4710): nm-CRITICAL **: 00:27:32.905: ((src/libnm-client-impl/nm-device.c:1141)): assertion '' failed
(io.elementary.wingpanel:4710): io.elementary.wingpanel.bluetooth-CRITICAL **: 00:27:57.975: Manager.vala:64: Error calling StartServiceByName for org.bluez: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)

As a result of all this it also freezes up occasionally requiring for me to kill the process manually or even restart the entire system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants