GNOME Bugzilla – Bug 783447
gnome-system monitor ate 500+MB of memory over a week.
Last modified: 2018-02-03 18:18:08 UTC
Created attachment 353210 [details] valgrind log I have noticed gnome-system monitor ate 500+MB or memory over a week. I have rebooted since but I am noticing a steady memory increase every time I switch the sorting of "Memory" column between ascending and descending in the process list or switch between "Resources" and "processes" tabs. I'm attaching a valgrind log.
Hello Hussam, you could confirm what version you are running ?
3.25.2 git revision 58ad557e. Latest pango from git master branch. Thank you.
Created attachment 353252 [details] valgrind showing 7MB leak. I found an easy way to replicate this. compile something like mesa which takes some time while looking at gnome-system-monitor. gnome-system-monitor seems to be getting confused when items disappear from the list and reappear in different order (memory usage order). The new valgrind log shows 7MB of leaks captured while compiling mesa and a few things (gcc, make, etc.. processes appearing in the process list and disappearing).
Don't worry Hussam, I can already tell where the issue is. The problem is a little bit bigger, we might have to revert some commits.
Fixed in the next release: https://git.gnome.org/browse/gnome-system-monitor/commit/?id=0ec44c66f46ed2f06105d63d45ee129f914499d1
Hi. Thank you for the fix. It looks like this now. https://pastebin.com/raw/CdViV92x Should I file a new bug for the pango issues?
What pango version are you running ?
Latest from git master branch (revision 148a5af3f66b504d3d36df3c6c45f218250a8a0a)
Is this still an issue for you? I did test with several Memory column sort changes and Resources/Processes tabs clicking back and forth, but didn't get any memory increase, it is steady 28.3 MiB for me with current master.
(In reply to Robert Roth from comment #9) > Is this still an issue for you? I did test with several Memory column sort > changes and Resources/Processes tabs clicking back and forth, but didn't get > any memory increase, it is steady 28.3 MiB for me with current master. No. It was fixed after the revision mentioned in comment #5. Thank you for the reminder. I will close the bug report.