xfdesktop memory leak

Chris Hilton chris129 at cs.iastate.edu
Sat May 28 22:47:31 CEST 2005

You must compile with debugging symbols, -g.  Then you need to run it
under valgrind (warning this is UNBELIEVABLY SLOW):
valgrind -v --tool=memcheck --leak-check=yes [program]

That will give you tons of text, and I don't know what it's printing to
(if I remember right some of it is stdout, some is stderr, and some is
something else) and at the bottom it should give a summary of memory
errors and leaks.  If you get error contexts and leak contexts outside
of the application (specifically in X) I believe these are just
something with gtk.

On Mon, 2005-05-23 at 11:20 -0700, Brian J. Tarricone wrote:
> Hash: SHA1
> Xavier Otazu wrote:
> > Hello:
> >
> > I guess xfdesktop has some kind of memory leak.
> >
> > I have an script which executes xfdesktop -reload every 10 minutes
> > in order to change desktop background image. My machine was running
> > all weekend, and today xfdesktop was using more than 50 Mb memory,
> > when usually it uses 10 Mb.
> >
> > I am sorry not supply more detailed analysis.
> Really the only way to debug this is to run xfdesktop through a memory
> profiling tool, like valgrind.  I haven't used it in a while, so I
> don't recall the exact usage for to get this type of information, and
> I don't have time at present to mess around with it.
>     -brian
> Version: GnuPG v1.4.1 (MingW32)
> iD8DBQFCkh8B6XyW6VEeAnsRAlbqAKCy9PF3cPCSXiyXIVPJAw/BoaeaNgCaAyj5
> rexWz3Ip0DmhzIoSalci2XI=
> =Yfor
> _______________________________________________
> Xfce4-dev mailing list
> Xfce4-dev at xfce.org
> http://foo-projects.org/mailman/listinfo/xfce4-dev

More information about the Xfce4-dev mailing list