Panel memory leak?

Peeter Vois Peeter.Vois at
Tue Sep 21 13:37:32 CEST 2004

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
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. 

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.

Best Regards ...

Jasper Huijsmans kirjutas T, 21.09.2004 kell 10:04:

> On Tue, Sep 21, 2004 at 09:50:31AM +0300, Peeter Vois wrote:
> > Hi,
> > 
> > Today morning when I opened my desktop from screensaver, I noticed that
> > panel was unable to start terminal. It told me that no memory. Then I
> > switched to text console and did run top command. The panel was
> > allocated over 300M memory. Yesterday I did play with the plugins and I
> > did add to the panel a trigger launcher, but I did forget to configure
> > it. Today I did need to restart the XFCE and the panel did take at the
> > beginning 20M of memory (7M is shared). Is this amount normal?
> > 
> 20M is a bit much (with 7M shared), but normal, 300M definitely is a big
> memleak :/
> I know he fstab plugin used to have a leak in version 0.1 (IIRC), but can't
> remember anything else.
> I did find a memleak when repeatedly killing and restarting xfce-msc-manager
> (still no idea why), but that seems to be unrelated.
> 	Jasper
> _______________________________________________
> Xfce4-dev mailing list
> Xfce4-dev at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Xfce4-dev mailing list