Bug 205245 - Excessive memory consumption (leak?) by setroubleshootd
Summary: Excessive memory consumption (leak?) by setroubleshootd
Keywords:
Status: CLOSED DUPLICATE of bug 204274
Alias: None
Product: Fedora
Classification: Fedora
Component: setroubleshoot
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: John Dennis
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-09-05 15:39 UTC by Dave Malcolm
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-07 20:10:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dave Malcolm 2006-09-05 15:39:01 UTC
Description of problem:
top - 11:33:52 up 3 days, 20:30,  4 users,  load average: 1.34, 1.03, 0.43
Tasks: 137 total,   3 running, 131 sleeping,   0 stopped,   3 zombie
Cpu(s): 63.1% us,  8.3% sy,  0.0% ni, 20.6% id,  6.0% wa,  2.0% hi,  0.0% si, 
0.0% st
  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND           
                                                       
 1589 root      16   0  797m 380m 1964 S  0.0 43.0   5:01.35 setroubleshootd   
                                 

Looks like a memory leak.  I don't know the precise policy for when garbage
collection happens in Python, though, maybe it's waiting for that instead?

Version-Release number of selected component (if applicable):
setroubleshoot-0.39-1

How reproducible:
Unknown; this was the result on returning to the machine, having left it up over
a long weekend.  The box is serving a web site, and there's a cronjob for
backups, so there would have been some latent activity on the box over that time.

Additional info:
An "AVC denial, click icon to view" notification is visible, but no SELinux icon
is visible in the notification area, so I can't click on it (do you want me to
file this as a separate bug?)

Comment 1 John Dennis 2006-09-07 20:10:40 UTC

*** This bug has been marked as a duplicate of 204274 ***


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