GNOME Bugzilla – Bug 564486
Memory leak
Last modified: 2008-12-15 18:01:07 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
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 ***