Panel memory leak?
edward.herr at charter.net
Tue Sep 21 14:18:23 CEST 2004
I also had a memory leak this week but it turned out to be a GTK problem in
2.4.9. GTK+ 2.4.10 fixes the leak. I am running xfce cvs from 9/10.
On Tue, 21 Sep 2004 13:45:08 +0200
Jasper Huijsmans <jasper at xfce.org> wrote:
> On Tue, Sep 21, 2004 at 02:37:32PM +0300, 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 did raise memory usage from 17M (initial) to 53M with some minutes.
> Ok, thanks, I'll have a look this evening, unless Danny will do so first.
> > Something more about panel memory usage: I noticed that the memory usage
> > did raise each time I did open a NEW popup menu. The usage did not
> > change when I reopened the popup. The usage did never reduce. So I
> > managed to raise memory usage by opening all popups by amount about 1M.
> > I know that gtk+ makes some magic with memory usage. That it more like
> > requires new chunk of memory and avoids to free it for better
> > performance at next time the memory will be needed again. It might be
> > the case.
> Yes, and the menus are created on first use and remain in memory afterwards.
> Xfce4-dev mailing list
> Xfce4-dev at xfce.org
More information about the Xfce4-dev