After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 587388 - Changing background makes xorg use more memory
Changing background makes xorg use more memory
Status: RESOLVED INCOMPLETE
Product: gnome-desktop
Classification: Core
Component: libgnome-desktop
2.24.x
Other Linux
: Normal critical
: ---
Assigned To: Desktop Maintainers
Desktop Maintainers
: 587387 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-06-30 04:47 UTC by Sven von Brand
Modified: 2010-05-24 13:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Sven von Brand 2009-06-30 04:47:16 UTC 
Steps to reproduce:
1. watch memory usage
2. change background many times
3. watch memory usage


Stack trace:


Other information:
xorg starts using more and more memory (ram) when the desktop wallpaper is changed, if it is done with an xml file to do an animation, this will make the pc crash eventually, because it will run out of memory. the problem seems to be in freeing the memory.
Comment 1 Sven von Brand 2009-06-30 05:14:14 UTC 
*** Bug 587387 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2009-06-30 09:25:02 UTC 
You should run valgrind to track this down.
In general this needs way more information - desktop windowmanager, version, ditribution etc.
Comment 3 Sven von Brand 2009-07-03 00:51:24 UTC 
Fedora 10 x86_64
It is posible to reproduce the bug with compiz and without compiz activated.
haven't been able to use valgrind to track Xorg, still trying.
Comment 4 Cosimo Cecchi 2009-07-08 11:32:29 UTC 
-> gnome-desktop

Nautilus uses GnomeBG to change the wallpaper, so the gnome-desktop product was actually right.
Comment 5 André Klapper 2010-03-27 19:57:33 UTC 
NEEDINFO - logs needed.
Comment 6 Tobias Mueller 2010-05-24 13:34:03 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!