Bug 869805 - gnome-screensaver is leaking ~21 MB of memory every lock/unlock cycle.
gnome-screensaver is leaking ~21 MB of memory every lock/unlock cycle.
Status: NEW
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-screensaver (Show other bugs)
6.6
x86_64 Linux
unspecified Severity medium
: rc
: ---
Assigned To: Ray Strode [halfline]
Desktop QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-24 16:23 EDT by Yeroc
Modified: 2017-09-14 07:57 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Yeroc 2012-10-24 16:23:36 EDT
As per summary, I'm seeing gnome-screensaver consuming more and more memory over time.  Every time the screen is locked and then unlocked it consumes an additional ~21 MB of memory.

This issue appears to be identical to an issue reported against FC10 (#533614) but I created a new issue because I didn't seem to have permissions to re-open that case.
Comment 1 RHEL Product and Program Management 2012-12-14 03:07:00 EST
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 2 Yeroc 2013-08-29 10:33:33 EDT
This remains an issue with the latest gnome-screensaver package (gnome-screensaver-2.28.3-24.el6_4.1.x86_64).
Comment 3 Yeroc 2014-03-13 11:10:42 EDT
I've retested with the latest gnome-screensaver package as of today (gnome-screensaver-2.28.3-28.el6.x86_64) and am still seeing this memory leak.  Really annoying to have to restart it every week or so to free up memory!

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