Bug 694149 - SSSD consumes GBs of RAM, possible memory leak
Summary: SSSD consumes GBs of RAM, possible memory leak
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: sssd
Version: 5.7
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Stephen Gallagher
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
: 694217 (view as bug list)
Depends On: 692251 694146 694217
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-06 15:17 UTC by Stephen Gallagher
Modified: 2015-01-04 23:47 UTC (History)
11 users (show)

Fixed In Version: sssd-1.5.1-29.el5
Doc Type: Bug Fix
Doc Text:
For large cache files, if a user was removed from a group in LDAP, memory allocation could grow exponentially while processing the removal from the cache, potentially resulting in an OOM (Out of Memory) situation. With this update, this issue has been fixed, and SSSD no longer allocates unnecessarily large amounts of memory when removing a user from a group in LDAP.
Clone Of: 694146
Environment:
Last Closed: 2011-07-21 08:11:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:0975 0 normal SHIPPED_LIVE Low: sssd security, bug fix, and enhancement update 2011-07-21 08:09:03 UTC

Comment 1 Dmitri Pal 2011-04-06 18:27:20 UTC
*** Bug 694217 has been marked as a duplicate of this bug. ***

Comment 3 Kaushik Banerjee 2011-05-10 14:37:13 UTC
Memory doesn't grow too large. Verified with the steps in bug 694146, comment 9

top - 14:24:07 up  5:05,  3 users,  load average: 0.92, 0.43, 0.19
Tasks:  86 total,   3 running,  83 sleeping,   0 stopped,   0 zombie
Cpu(s): 96.3%us,  2.7%sy,  0.0%ni,  0.0%id,  0.0%wa,  1.0%hi,  0.0%si,  0.0%st
Mem:  15044224k total,   709804k used, 14334420k free,    71888k buffers
Swap:  9240568k total,        0k used,  9240568k free,   421928k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND     
  759 root      25   0  150m  99m  16m R 99.6  0.7   3:04.94 ldbmodify         


top - 14:27:34 up  5:09,  3 users,  load average: 1.01, 0.72, 0.35
Tasks:  86 total,   3 running,  83 sleeping,   0 stopped,   0 zombie
Cpu(s): 98.0%us,  1.3%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.7%hi,  0.0%si,  0.0%st
Mem:  15044224k total,   734232k used, 14309992k free,    72104k buffers
Swap:  9240568k total,        0k used,  9240568k free,   421928k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND            
  759 root      25   0  169m 119m  17m R 99.3  0.8   6:00.99 ldbmodify       


Verified in version:
# rpm -qi sssd | head
Name        : sssd                         Relocations: (not relocatable)
Version     : 1.5.1                             Vendor: Red Hat, Inc.
Release     : 34.el5                        Build Date: Tue 03 May 2011 10:46:07 PM IST
Install Date: Tue 10 May 2011 09:50:38 AM IST      Build Host: x86-003.build.bos.redhat.com
Group       : Applications/System           Source RPM: sssd-1.5.1-34.el5.src.rpm
Size        : 3486753                          License: GPLv3+
Signature   : (none)
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL         : http://fedorahosted.org/sssd/
Summary     : System Security Services Daemon

Comment 4 Miroslav Svoboda 2011-07-15 13:30:15 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
For large cache files, if a user was removed from a group in LDAP, memory allocation could grow exponentially while processing the removal from the cache, potentially resulting in an OOM (Out of Memory) situation. With this update, this issue has been fixed, and SSSD no longer allocates unnecessarily large amounts of memory when removing a user from a group in LDAP.

Comment 5 errata-xmlrpc 2011-07-21 08:11:33 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-0975.html


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