GNOME Bugzilla – Bug 341175
gnome-system-monitor leaks
Last modified: 2011-11-11 10:03:55 UTC
Please describe the problem: g-s-m seems to have a slow memory leak Steps to reproduce: 1. Open GSM 2. Stay on the resources tab 3. Keep it open for 10 hours Actual results: My writable memory size grew to > 20 MB. Keeping it open for a few more hours, it grew to 25 mb Expected results: No leaks Does this happen every time? Yes Other information:
Created attachment 65118 [details] [review] fix small leak i think that's not the main leak, but that's still one.
Created attachment 65167 [details] [review] more fix previous fix + free some stuff atexit.
Created attachment 65172 [details] valgrind output it's leaking pixbufs
may be not. something is wrong with gtk_icon_theme_load_icon
Benoit, you may want to pass --leak-resolution=high. It will give you more detailed data about leaks. VG aggregates data from multiple leaks into one. However, the default resolution is low, which often combines too much.
i did run valgrind during all the night. No obvious leak :/ ==18883== LEAK SUMMARY: ==18883== definitely lost: 2,892 bytes in 50 blocks. ==18883== indirectly lost: 120 bytes in 10 blocks. ==18883== possibly lost: 170,083 bytes in 215 blocks. ==18883== still reachable: 1,424,903 bytes in 28,508 blocks. ==18883== suppressed: 0 bytes in 0 blocks.
Created attachment 68557 [details] massif output still here :/
I just can fix this bug. Valgrind sucks. Especially memcheck. I've never been able to use it on something more elaborated than /bin/ls. Even on 3GHz computer, it takes 100% CPU and system-monitor is just unusable. I can't believe someone ever run any graphical app with it. On my slower laptop, i simply never get the window painted, even after 10minutes. So if anyone knows some decent tool that can run on a non-quantic computer, i'll try it.
The memalign suggests that this is coming from gslice allocated things. You may want to think about where such allocations might be made. Also, consider passing the --depth=5 flag when using massif this will give you some details about callers lower in the stack in the .txt file
There were huge leaks in clearlooks which are now fixed. May be there are still small leaks, but it doesn't leak many MB a day anymore.
I left system-monitor run for 48H, no leaks. That was definitely clearlooks.