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 564486 - Memory leak
Memory leak
Status: RESOLVED DUPLICATE of bug 564548
Product: gnome-screensaver
Classification: Deprecated
Component: general
unspecified
Other Linux
: Normal major
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2008-12-14 14:04 UTC by 28872d13
Modified: 2008-12-15 18:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description 28872d13 2008-12-14 14:04:56 UTC
gnome-screensaver seems to leak X pixmap memory for some reason.

Reproduce:
1. Start xrestop
2. Note that everything is fine
3. Inhibit the screensaver (I'm using the picture slideshow screensaver)
4. Wait for some time (I left it running for about two hours)

Now either some 15000K "<unknown>" blocks appear in xrestop or gnome-screensaver uses a whole lot of pixmap mem (for me 108000K). The "<unknown>" blocks won't disappear even when gnome-screensaver is killed.

Looks roughly like that:

xrestop - Display: localhost:0
          Monitoring 93 clients. XErrors: 0
          Pixmaps:  517053K total, Other:     141K total, All:  517194K total

res-base Wins  GCs Fnts Pxms Misc   Pxm mem  Other   Total   PID Identifier    
0c00000    12   28    2   72 1029    20759K     27K  20786K 30674 metacity
d200000     0    0    0    1    0    15000K      0B  15000K   ?   <unknown>
d000000     0    0    0    1    0    15000K      0B  15000K   ?   <unknown>
cc00000     0    0    0    1    0    15000K      0B  15000K   ?   <unknown>
ca00000     0    0    0    1    0    15000K      0B  15000K   ?   <unknown>
c800000     0    0    0    1    0    15000K      0B  15000K   ?   <unknown>
c600000     0    0    0    1    0    15000K      0B  15000K   ?   <unknown>
c400000     0    0    0    1    0    15000K      0B  15000K   ?   <unknown>
c200000     0    0    0    1    0    15000K      0B  15000K   ?   <unknown>
c000000     0    0    0    1    0    15000K      0B  15000K   ?   <unknown>
be00000     0    0    0    1    0    15000K      0B  15000K   ?   <unknown>
bc00000     0    0    0    1    0    15000K      0B  15000K   ?   <unknown>
[...]

Some possible factors:
- nvidia proprietary driver
- metacity + compositing
- two monitors

See also http://bbs.archlinux.org/viewtopic.php?pid=463791
Comment 1 Ray Strode [halfline] 2008-12-15 18:01:07 UTC
Thanks for taking the time to report this bug.
This particular bug has been reported into our bug tracking system as bug 564548 and we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 564548 ***