GNOME Bugzilla – Bug 91916
Major memory leakage
Last modified: 2004-12-22 21:47:04 UTC
relevant hardware: p3 866mhz with 384M PC100 SDRAM pan uses about 11mb of RAM at startup, which jumps to 16mb upon opening a group, which jumps to ~20mb upon opening an article; this ram usage continues to grow until pan uses all available ram and the kernel kills the process: [avenj@cerberus avenj]$ grep pan /var/log/messages Aug 28 17:01:13 cerberus kernel: Out of Memory: Killed process 31903 (pan). Aug 28 17:01:13 cerberus kernel: Out of Memory: Killed process 31904 (pan). Aug 28 17:01:13 cerberus kernel: Out of Memory: Killed process 31906 (pan). Aug 28 17:01:13 cerberus kernel: Out of Memory: Killed process 31907 (pan). Aug 28 17:01:13 cerberus kernel: Out of Memory: Killed process 31908 (pan). Aug 28 17:01:13 cerberus kernel: Out of Memory: Killed process 31909 (pan).
Wow!! I can't reproduce any of this, but certainly would like to know what's going on there. Any chance you could run Pan inside of valgrind for me? Typically "valgrind --logfile-fd=9 --num-callers=16 --leak-check=yes --leak-resolution=high pan 9>logfile"
I would, but valgrind has never worked properly on my box and I'm not entirely sure why: [avenj@cerberus valgrind-1.0.1]$ valgrind --logfile-fd=9 --num-callers=16 --leak-check=yes --leak-resolution=high pan 9>logfile valgrind's libpthread.so: libc_internal_tsd_get: invalid key valgrind's libpthread.so: libc_internal_tsd_get: invalid key ..and then quits. Is there any similar software? Also, do you need any information on related libraries and the like?
Hmm, frustrating, Does valgrind 1.0.2 fare any better?
Nope, same issue, although I note that it works with all applications other than those using GTK. Perhaps I have broken GTK libs? [avenj@cerberus avenj]$ rpm -q gtk+ gtk+-1.2.10-21 [avenj@cerberus avenj]$ rpm -q gtk2 gtk2-2.0.6-8
Aha, I think I've fixed this! Try updating to a CVS snapshot, or just give this patch a spin: http://cvs.gnome.org/bonsai/cvsview2.cgi?diff_mode=context&whitespace_mode=show&subdir=pan/pan/base&command=DIFF_FRAMESET&file=util-mime.c&rev1=1.42&rev2=1.43&root=/cvs/gnome
Yeah, that did fix the consistently leaking - although I note that for every (completely plain text) message I open RAM usage jumps about five megabytes higher... But yes, no more extremely excessive leaks :-)
Thanks for pointing it out. I tracked that down and fixed it too... :)