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 557602 - multiload memory leak
multiload memory leak
Status: RESOLVED FIXED
Product: gnome-applets
Classification: Other
Component: multiload
2.24.x
Other All
: Normal major
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-10-23 12:43 UTC by Brian J. Murrell
Modified: 2009-01-20 05:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24

Attachments
fix from ubuntu folks that fixes the leak (581 bytes, patch)
2008-12-26 14:21 UTC, David Mansfield 		none Details | Review

Description Brian J. Murrell 2008-10-23 12:43:42 UTC 
Please describe the problem:
I'm seeing a memory leak in the multiload-applet-2.  It crept up to 142M VM and 123M resident and when I simply killed it (so that gnome prompted me to restart it) on restart it was only 22M/9.3M.

Wow.  even 22M seems a lot for such a simple little applet.

Steps to reproduce:
1. start multiload-applet-2
2. wait
3. measure


Actual results:
multiload's footprint grows

Expected results:
remain consistent

Does this happen every time?
yes

Other information:
Comment 1 David Mansfield 2008-12-26 14:20:28 UTC 
The ubuntu guys have tracked this down and fixed their version.  Not sure where the communication is supposed to be there.  See: 

https://bugs.launchpad.net/ubuntu/intrepid/+source/libgtop2/+bug/307472

I'm going to attach the fix that was applied there, courtesy of Brian Downing, I believe.
Comment 2 David Mansfield 2008-12-26 14:21:00 UTC 
Created attachment 125343 [details] [review]
fix from ubuntu folks that fixes the leak
Comment 3 David Mansfield 2009-01-19 20:17:50 UTC 
can anything be done to move this along?
Comment 4 Callum McKenzie 2009-01-20 05:37:30 UTC 
This should really have been reported to libgtop (thats what the patch applies to). Fortunately, it looks as though this leak has been fixed, so replacing libgtop with a recent version should fix the leak.