Panel memory leak?
fourdan at xfce.org
Tue Sep 21 22:21:55 CEST 2004
GTK FAQ clearly states that "top" should not be used for tracking
"memory leak" : http://www.gtk.org/faq/#AEN703
If you really want to track a memory leak, better use valgrind...
On Tue, 2004-09-21 at 21:54, Jasper Huijsmans wrote:
> Peeter Vois wrote:
> > Hi !
> > I did play a little more with possibilities and top, and I did find that
> > the memory leak works rock-solid. Here comes step by step how to do it:
> > 1. Add to the panel the trigger launcher,
> > 2. Do not fill any inputboxes,
> > 3. For better memory leak performance make it check every second the
> > condition,
> > 4.Start terminal and watch the `top` output 'M' key will show most
> > memory requiring app at the top
> > 5. For safety do not let it work too long time
> > 6. Remove the trigger launcher from the panel
> > 7. Notice that the panel does not free the memory allocated during the
> > trigger launcher did work.
> I'm afraid I can't reproduce this in the CVS version :/ Does anyone else
> see this?
> Xfce4-dev mailing list
> Xfce4-dev at xfce.org
- Olivier Fourdan - fourdan at xfce.org - http://www.xfce.org -
More information about the Xfce4-dev