Bug 1292543

Summary:	[BUG] accounts-daemon process memory grows until all memory is gone
Product:	Red Hat Enterprise Linux 7	Reporter:	Sam Roza <sroza>
Component:	accountsservice	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.1	CC:	pdhamdhe, qguo, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	accountsservice-0.6.35-11.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-04 07:51:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sam Roza 2015-12-17 17:51:54 UTC

Description of problem: Over time, on servers with frequent SSH connections, the accounts-daemon grows very large until the server is out of memory and causes OOMs.


Version-Release number of selected component (if applicable):
 Accountsservice-0.6.35-7

How reproducible:
 Always.

Steps to Reproduce:
1. Install RHEL 7.1
2. Enable graphical target
3. Log into server frequently using SSH
4. Monitor size of accounts-daemon process

Actual results:
 accounts-daemon process continues to grow until all memory is gone

Expected results:
 accounts-daemon should not consume as much memory as possible

Additional info:
 Workaround exists: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1316830

sudo mv /usr/share/dbus-1/system-services/org.freedesktop.Accounts.service /usr/share/dbus-1/system-services/org.freedesktop.Accounts.service.disabled

Comment 7 errata-xmlrpc 2016-11-04 07:51:49 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2522.html