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 483635 - Memory leak when an icon disappears
Memory leak when an icon disappears
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: notification area
2.20.x
Other Linux
: Normal major
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-05 08:34 UTC by Josselin Mouette
Modified: 2011-05-20 12:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Josselin Mouette 2007-10-05 08:34:31 UTC
[ forwarded from http://bugs.debian.org/445340 by Mike Hommey ]

> After a few hours running, here is what top displays:
> 7816 mh        15   0  266m 167m 6788 S  0.7 22.1   4:25.10 gnome-panel
> 
> There is obviously something leaking.

I think i found the culprit. My battery is half dead, and the
gnome-power-manager notification icon is set up to only show up when on
battery. As it happens, the acpi information switches quite randomly
between on battery an on AC, meaning the icon appears/disappears quite a
lot, and following gnome-panel memory usage after a while seems to
indicate the memory hogging doesn't happen when the icon is made still
(always display it), though the icon itself changes (switches between the
charging icon and the on AC icon).

So, on first hand, there seems to be a leak when a notification icon
disappears.
Comment 1 Vincent Untz 2007-11-13 09:47:53 UTC
Of course, a valgrind log would help :-)
Comment 2 Kjartan Maraas 2008-01-07 10:44:29 UTC
The only leak I found from testing with the evolution notification icon was this:
==24069== 756 (280 direct, 476 indirect) bytes in 7 blocks are definitely lost in loss record 133 of 188
==24069==    at 0x402498E: calloc (vg_replace_malloc.c:397)
==24069==    by 0x4B292DD: g_malloc0 (gmem.c:150)
==24069==    by 0x49F6E92: ORBit_objref_new (corba-object.c:152)
==24069==    by 0x49F76CF: ORBit_objref_find (corba-object.c:196)
==24069==    by 0x49F78B8: ORBit_demarshal_object (corba-object.c:612)
==24069==    by 0x49FDDB7: ORBit_demarshal_value (corba-any.c:533)
==24069==    by 0x49F4514: orbit_small_demarshal (orbit-small.c:425)
==24069==    by 0x49F4D9B: ORBit_small_invoke_stub (orbit-small.c:663)
==24069==    by 0x49F4F8D: ORBit_small_invoke_stub_n (orbit-small.c:575)
==24069==    by 0x4A021A1: ORBit_c_stub_invoke (poa.c:2643)
==24069==    by 0x420998D: Bonobo_Control_getPopupContainer (Bonobo-stubs.c:981)
==24069==    by 0x413C187: bonobo_control_frame_get_popup_component (bonobo-control-frame.c:1136)

Not sure if that's related though.
Comment 3 Vincent Untz 2011-04-06 12:02:31 UTC
I wonder if http://git.gnome.org/browse/gnome-panel/commit/?id=41d0e690edfe952a4ff8b8f6ea01cb9cb09695f7 fixes this. Could you potentially check?
Comment 4 Akhil Laddha 2011-05-20 12:42:35 UTC
Josselin, were you able to test the fix mentioned in comment#3 ?
Comment 5 Josselin Mouette 2011-05-20 12:50:03 UTC
(In reply to comment #4)
> Josselin, were you able to test the fix mentioned in comment#3 ?

The user who reported this doesn’t have anymore the problem of the blinking power icon, so he cannot reproduce the bug anyway.

I’d say, let’s assume this has been fixed.