Bug 468339 - Excessive memory leak when changing background wallpaper
Summary: Excessive memory leak when changing background wallpaper
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-desktop
Version: rawhide
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-24 08:24 UTC by Mamoru TASAKA
Modified: 2008-12-06 14:48 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-12-05 14:36:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
memory usage of X (22.47 KB, text/plain)
2008-10-24 08:25 UTC, Mamoru TASAKA
no flags Details

Description Mamoru TASAKA 2008-10-24 08:24:45 UTC
Description of problem:
Every time I change the background wallpaper on GNOME
the memory usage of X increases and never decreases.

Version-Release number of selected component (if applicable):
control-center-2.24.0.1-8.fc10.i386
metacity-2.24.0-2.fc10.i386
xorg-x11-server-Xorg-1.5.2-8.fc10.i386

Adding to F10DesktopBlocker for now. Please triage.

How reproducible:
100%

Steps to Reproduce:
1. login to GNOME
2. launch gnome-appearance-properties
3. choose Background
4. change wallpaper again and again
5. see the memory usage of Xorg
  
Actual results:
Attached.
Here at last Xorg uses more than 1G memories.

Expected results:
Xorg memory usage should not increase

Comment 1 Mamoru TASAKA 2008-10-24 08:25:35 UTC
Created attachment 321379 [details]
memory usage of X

Comment 2 Ray Strode [halfline] 2008-10-24 18:46:07 UTC
hmm running xrestop on nautilus I get a constant 21 pixmaps after switching the background many times.

memory usage did go up though.

top first reported

2% memory usage and by the end reported 3.2% memory usage.

Mamoru, does that jive with what you're seeing?  xrestop shows no resource increases, but xserver memory usage goes up?

Comment 3 Mamoru TASAKA 2008-10-25 01:18:24 UTC
Well,

(In reply to comment #2)
> hmm running xrestop on nautilus 

On my usage:
[tasaka1@localhost ~]$ gconftool-2 --get /apps/nautilus/preferences/show_desktop
false

and xrestop says (after switching wallpaper repeatedly)

xrestop - Display: localhost:0
          Monitoring 56 clients. XErrors: 0
          Pixmaps:  362052K total, Other:     133K total, All:  362186K total

res-base Wins  GCs Fnts Pxms Misc   Pxm mem  Other   Total   PID Identifier    
1a00000     8   28    0  112  209   380928K	 5K 380933K 30822 gnome-settings-daemon

Comment 4 Matthias Clasen 2008-10-26 22:39:11 UTC
Whats the verdict here ? memleak gone or not ?

Comment 5 Mamoru TASAKA 2008-10-27 04:39:45 UTC
Still I see this memleak.

Comment 6 Ray Strode [halfline] 2008-10-27 14:54:54 UTC
I can reproduce this to, by disabling nautilus.

We leak 1 pixmap every fade.

It's probably a bug in gnome-desktop that only gnome-settings-daemon is hitting and nautilus is missing.

Comment 7 Ray Strode [halfline] 2008-10-27 19:19:53 UTC
This should be fixed in tomorrow's rawhide.

Comment 8 Mamoru TASAKA 2008-10-28 14:02:57 UTC
Seems good, thanks!

Comment 9 Mamoru TASAKA 2008-12-05 08:46:00 UTC
It seems that this issue is reappearing with gnome-desktop-2.25.2-3.fc11.

Comment 10 Mamoru TASAKA 2008-12-05 08:51:01 UTC
Again:

$ gconftool-2 --get /apps/nautilus/preferences/show_desktop
false

xrestop report:
res-base Wins  GCs Fnts Pxms Misc   Pxm mem  Other   Total   PID Identifier    
1800000     8   28    0  130  206   460288K      5K 460293K  9307 gnome-settings-daemon

ps auwwx report:
root      2567  6.6 36.8 558952 278936 tty7    Ss+  15:36   8:56 /usr/bin/Xorg :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-sXRNeh/database -nolisten tcp

Comment 11 Ray Strode [halfline] 2008-12-05 14:27:12 UTC
looking through the diff between before the old patch and the updated patch I see this:

- g_object_ref (old_pixmap);

in gnome_bg_set_pixmap_as_root_with_crossfade ().

Will fix.  Thanks for picking up on this so quickly.

Comment 12 Ray Strode [halfline] 2008-12-05 14:36:41 UTC
should be fixed in the latest (still building) build.

Comment 13 Mamoru TASAKA 2008-12-06 14:48:04 UTC
Yes, it is fixed, thank you.


Note You need to log in before you can comment on or make changes to this bug.