FS#15939 - [gnome-panel] wnck-applet memory leak

Attached to Project: Arch Linux
Opened by Vitaliy (ngsupb) - Saturday, 15 August 2009, 09:54 GMT
Last edited by Jan de Groot (JGC) - Saturday, 21 November 2009, 17:00 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The bug exists in gnome.
wnck-applet grows in ram while Windows list applet is running.

After running my desktop for 3 days, the whck-applet was about 300 mb

Additional info:
* package version(s)
* config and/or log files etc.

The latest Arch linux packages.

Steps to reproduce:

1. Make sure Windows list applet is running
2. Start to switch between Workspaces
3. After some switches you will notice whck-applet takes more ram.

So when you work for a long time without reboot it will take a lot of ram.
This task depends upon

Closed by  Jan de Groot (JGC)
Saturday, 21 November 2009, 17:00 GMT
Reason for closing:  Works for me
Comment by Vitaliy (ngsupb) - Saturday, 15 August 2009, 10:00 GMT
oh there is other faster way to reproduce. You don't have to switch between workspaces, just right click on the Window List applet and click then on the move option and move from right to the lest the applet. The memory of whck-applet and gnome-panel grows very fast.
Comment by Vitaliy (ngsupb) - Saturday, 15 August 2009, 10:12 GMT
Well I can't reproduce this issue anymore after I removed the default Panel and set up the window list applet into a new one.
It appears this issue was with the original panel that comes with gnome :D
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 15 August 2009, 16:33 GMT
  • Field changed: Category (Packages: Extra → Upstream Bugs)
Please report this to upstream: http://bugzilla.gnome.org/
Remember to provide more details and versions of involved software.
Comment by Jan de Groot (JGC) - Sunday, 08 November 2009, 22:45 GMT
Still an issue with 2.28.0?

Loading...