After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 783447 - gnome-system monitor ate 500+MB of memory over a week.
gnome-system monitor ate 500+MB of memory over a week.
Status: RESOLVED FIXED
Product: system-monitor
Classification: Core
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2017-06-05 18:33 UTC by Hussam Al-Tayeb
Modified: 2018-02-03 18:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
valgrind log (52.92 KB, text/x-log)
2017-06-05 18:33 UTC, Hussam Al-Tayeb
Details
valgrind showing 7MB leak. (60.06 KB, text/x-log)
2017-06-06 10:26 UTC, Hussam Al-Tayeb
Details

Description Hussam Al-Tayeb 2017-06-05 18:33:27 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.
Comment 1 Benoît Dejean 2017-06-06 08:48:16 UTC
Hello Hussam, you could confirm what version you are running ?
Comment 2 Hussam Al-Tayeb 2017-06-06 08:51:13 UTC
3.25.2 git revision 58ad557e.
Latest pango from git master branch.
Thank you.
Comment 3 Hussam Al-Tayeb 2017-06-06 10:26:17 UTC
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).
Comment 4 Benoît Dejean 2017-06-06 12:06:19 UTC
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.
Comment 6 Hussam Al-Tayeb 2017-06-15 07:35:02 UTC
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?
Comment 7 Benoît Dejean 2017-06-15 07:42:32 UTC
What pango version are you running ?
Comment 8 Hussam Al-Tayeb 2017-06-15 07:45:18 UTC
Latest from git master branch (revision 148a5af3f66b504d3d36df3c6c45f218250a8a0a)
Comment 9 Robert Roth 2018-02-03 18:00:39 UTC
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.
Comment 10 Hussam Al-Tayeb 2018-02-03 18:18:08 UTC
(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.