Hide Forgot
Description of problem: Upon locking and unlocking the terminal gnome-screensaver uses ~9.3MiB of memory. Version-Release number of selected component (if applicable): # rpm -qa | grep screensa gnome-screensaver-2.28.3-8.el6.i686 How reproducible: Always Steps to Reproduce: 1. Log into machine 2. Check memory usage of gnome-screensaver 3. Lock screen 4. Unlock screen Actual results: Memory used by gnome-screensaver goes up ~9MiB indefinitely Expected results: May use more memory initially, but should release memory after a period of time Additional info: Similar to bug on Fedora 12 https://bugzilla.redhat.com/show_bug.cgi?id=533614 However, this does not seem to have a cap. My system is currently using 687.0MiB for gnome-screensaver. That bug shows no resolution. Also found a similar bug reported against RHEL 5.4 saying that x11perf-umove but says it was fixed in RHEL 6. Not sure if it is related, but probably worth mentioning. I was able to re-create this issue on 3 different systems that I tried, all running RHEL6 workstation. (We are currently "beta" testing RHEL 6.0 for replacement of machines at my company).
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
From a run of gnome-screensaver in valgrind: ==2443== 12,288,000 bytes in 1 blocks are possibly lost in loss record 4,070 of 4,070 ==2443== at 0x4025BDC: malloc (vg_replace_malloc.c:195) ==2443== by 0x5A9088: g_try_malloc (in /lib/libglib-2.0.so.0.2200.5) ==2443== by 0xA9C3CF: gdk_pixbuf_new (in /usr/lib/libgdk_pixbuf-2.0.so.0.1800.9) ==2443== by 0x476FBB8: ??? (in /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so) ==2443== by 0xAA1F00: ??? (in /usr/lib/libgdk_pixbuf-2.0.so.0.1800.9) ==2443== by 0xAA2227: gdk_pixbuf_new_from_file (in /usr/lib/libgdk_pixbuf-2.0.so.0.1800.9) ==2443== by 0x75C00E7: ??? (in /usr/lib/libgnome-desktop-2.so.11.4.2) ==2443== by 0x75C1FE8: ??? (in /usr/lib/libgnome-desktop-2.so.11.4.2) ==2443== by 0x75C274F: gnome_bg_draw (in /usr/lib/libgnome-desktop-2.so.11.4.2) ==2443== by 0x75C2883: gnome_bg_create_pixmap (in /usr/lib/libgnome-desktop-2.so.11.4.2) ==2443== by 0x80569CD: ??? (in /usr/bin/gnome-screensaver) ==2443== by 0x68D413: g_cclosure_marshal_VOID__VOID (in /lib/libgobject-2.0.so.0.2200.5) So the real culprit is gnome-desktop. Reassigning to correct component.
This has been fixed upstream with the following commit: http://git.gnome.org/browse/gnome-desktop/commit/?id=af477956ddd06e3821bbcc3e9337a637fe91584a Patch applies directly to RHEL-6 source.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2050 jroys3 20 0 3190m 2.3g 5496 S 0.0 28.9 3:01.33 gnome-screensav gnome-screensaver-2.28.3-8.el6.x86_64 gnome-desktop-2.28.2-8.el6.x86_64 11:26:35 up 68 days, 23:18, 29 users, load average: 0.09, 0.09, 0.09
The fix for this bug has been identified as the fix for rhbz#639732 also, FYI.
Bug 639732 is going to be fixed in upcoming RHEL release, closing this one as a duplicate. The issue and the patch are practically equal. FYI, since GnomeBG is used in several Gnome components, this might affect gnome-settings-daemon as well when nautilus is set not to draw the desktop. *** This bug has been marked as a duplicate of bug 639732 ***