GNOME Bugzilla – Bug 618952
Leak in gnome-power-manager on Ubuntu 10.04
Last modified: 2010-05-19 21:37:47 UTC
Created attachment 161303 [details] Abbreviated memcheck output See https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/569273 I have a Valgrind trace, although it's not particularly revealing without debug symbols.
Your log does indeed show 220 bytes being lost, although without debugging symbols the trace is worthless.
I'll try and get debug symbols. But to be clear, the observed behavior of GPM outside valgrind is a *huge* memory leak -- much more than 220 bytes. It's possible that I didn't run valgrind for long enough to see more than one instance of the leak. But I suspect that the blocks being reported as "possibly lost" are actually responsible for the leak I've observed. The full log, from a run of about 2 min, is 1.5mb long, and all of it is blocks possibly lost. Perhaps someone else could confirm whether it's normal to have so many blocks possibly lost, or if that's indicative of a problem.
If you're looking at possibly lost too, you'll need to install a *ton* of debug symbols.
(In reply to comment #3) > If you're looking at possibly lost too, you'll need to install a *ton* of debug > symbols. I was just going to build and run GPM with -g. Do you think that won't be sufficient?
Here's a Valgrind trace with debug symbols from the Launchpad bug: http://launchpadlibrarian.net/48685406/gpm.log
I still can only see 236 bytes lost. Also, the code where most of those is lost is not present in gnome-power-manager git master. Maybe try with --show-reachable=yes -- although I'm not sure what's going to show anything much more interesting.
Trace with --show-reachable=yes http://launchpadlibrarian.net/48727458/gpm-reachable.log
You're hemorrhaging memory from app_indicator_set_menu(), which is an Ubuntu Specific "value added" feature that gnome-power-manager has been patched with, as they didn't work with other people to get libappindicator upstream into the toolkit where it belongs. I'm quite angry now. My time has been wasted on this bug. File it on launchpad.
Very sorry for wasting your time, Richard. Thanks for identifying the problem.