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 627044 - wnck-applet has memory leak
wnck-applet has memory leak
Status: RESOLVED OBSOLETE
Product: libwnck
Classification: Core
Component: general
2.30.x
Other Linux
: Normal major
: ---
Assigned To: libwnck maintainers
libwnck maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-16 12:49 UTC by Massimo Cora'
Modified: 2018-01-24 13:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
valgrind log (222.36 KB, text/plain)
2010-09-15 15:05 UTC, Massimo Cora'
Details
leak -shot (31.86 KB, image/jpeg)
2010-09-22 14:53 UTC, Massimo Cora'
Details

Description Massimo Cora' 2010-08-16 12:49:02 UTC
I'm reporting the bug filed here

https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/576751

because I think that a deep investigation should be done to avoid system collapsing due to the big mem leak involved.
Comment 1 Massimo Cora' 2010-09-15 10:37:57 UTC
any news guys?
Comment 2 Vincent Untz 2010-09-15 10:50:43 UTC
We need a valgind log...
Comment 3 Massimo Cora' 2010-09-15 15:05:40 UTC
Created attachment 170346 [details]
valgrind log

A launchpad user took a valgrind log.
I attach it here together with the description of the steps to take it.

sudo apt-get install valgrind

sudo killall wnck-applet (this removes all 4 applets from bottom panel, except trash)

G_SLICE=always-malloc G_DEBUG=gc-friendly /usr/bin/valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log /usr/lib/gnome-panel/wnck-applet

let valgrind run for about 1 minute until it stops

post log file: /home/username/valgrind.log
Comment 4 Vincent Untz 2010-09-15 15:17:12 UTC
I quickly looked at it already, and there was no real sign of leak in the details. So a new one is needed, I guess.
Comment 5 Massimo Cora' 2010-09-22 14:53:49 UTC
Created attachment 170838 [details]
leak -shot

I'm gonna take a valgrind log myself. Here it a screenshot of the amount of memory used.
My current uptime is

$ uptime 
 16:53:47 up 26 days,  5:14,  8 users,  load average: 1.16, 1.40, 1.29

but I've already restarted wnkc once.
Comment 6 Massimo Cora' 2010-09-22 15:02:48 UTC
I've found some steps to reproduce the leak:

1. open system monitor
2. highlight wnck-applet so that it follows focus
3. press ctrl-alt-shift and right arrow/left arrow to switch between virtual desktops (I've 6 on my setup).
4. memory grows up about of 0.3 MB at every switch.

valgrind log seems tricky to take because the application is somehow detached and log ends in a few seconds.
Comment 7 Massimo Cora' 2010-09-22 15:12:05 UTC
this does NOT happen with fedora 12 and ubuntu 10.04 with compiz activated.

I've no compiz activated and I'm on an ubuntu 10.04.
The memory thing grows up a lot here.
Comment 8 MT 2010-10-27 05:55:58 UTC
Reading the report at https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/17787 might give a clue to the source of the problem. The panel with the wnck-applet needs to be have both auto-hide and transparency enabled for the memory leak to show up. After disabling transparency by changing the panel background to None (but keeping auto-hide enabled), I am no longer seeing the memory leak on my system.
Comment 9 GNOME Infrastructure Team 2018-01-24 13:49:38 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/libwnck/issues/119.