User-Agent: Opera/9.22 (X11; Linux i686; U; de) Build Identifier: Xfdesktop still leaks memory and slows down startup of applications the longer it runs. Attached is a valgrind log recorded with "-v --leak-check=yes --leak-resolution=high --num-callers=50 --log-file=xfdesktop xfdesktop". Desktop icons where not enabled here, startup notifcations where. Reproducible: Always Steps to Reproduce: 1. Use xfdesktop for a day or longer Actual Results: A memory leak occurs. Expected Results: Memory usage should stay the same.
Created attachment 1305 Valgrind logfile Xfdesktop running within valgrind for more than a day
After I gunzip this, it's still a binary file. Please just attach an uncompressed file. We have plenty of disk space.
> After I gunzip this, it's still a binary file. Please just attach an > uncompressed file. We have plenty of disk space Really weird. I also gunzipped the file and got my old logfile back. No binary stuff whatsoever. Anyways, the uncompressed logfile is attached now.
Created attachment 1307 Valgrind logfile (uncompressed) Xfdesktop running within valgrind for more than a day
(In reply to comment #4) > Created an attachment (id=1307) [details] > Valgrind logfile (uncompressed) > > Xfdesktop running within valgrind for more than a day > Sorry, this file didn't contain any details on _what_ memory blocks were leaked and _where_. Perhaps you didn't shut down xfdesktop or valgrind correctly? I'd suggest xfdesktop --quit.
(In reply to comment #5) > (In reply to comment #4) > > Created an attachment (id=1307) [details] [details] > > Valgrind logfile (uncompressed) > > > > Xfdesktop running within valgrind for more than a day > > > > Sorry, this file didn't contain any details on _what_ memory blocks were leaked > and _where_. Perhaps you didn't shut down xfdesktop or valgrind correctly? Yeah, I had to kill valgrind IIRC since it didn’t react to [Ctrl]+[C]. > I'd > suggest xfdesktop --quit. I’m currently doing another valgrind run and will try that.
(In reply to comment #6) > > I'd > > suggest xfdesktop --quit. > > I’m currently doing another valgrind run and will try that. I did and this didn’t help either. Once again, only SIGKILL could help. I’ll attach the new log, if it isn’t helpful either, then there isn’t much I can do anymore. (The huge leak+lag while running xfdesktop4 through valgrind even resulted in the OOM killer becoming active and killing my Thunderbird.)
Created attachment 1354 Another valgrind run
*** This bug has been marked as a duplicate of bug 2427 ***