Bug 499364 - setroubleshootd is using a ridiculous amount of memory
Summary: setroubleshootd is using a ridiculous amount of memory
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: setroubleshoot
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-06 11:23 UTC by James Morris
Modified: 2009-05-06 12:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-05-06 12:32:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description James Morris 2009-05-06 11:23:46 UTC
Description of problem:

# ps -F -C  setroubleshootd
UID        PID  PPID  C    SZ   RSS PSR STIME TTY          TIME CMD
root      1651     1  0 78094 70508   0 14:52 ?        00:00:02 /usr/bin/python -E /usr/sbin/setroubleshootd -f


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

setroubleshoot-2.1.8-1.fc11.x86_64


Additional info:

People might hate SELinux a little less if we can reduce the memory used by this.

Comment 1 Daniel Walsh 2009-05-06 11:53:27 UTC
This is a problem with python.  setroubleshoot should only be running for very short times now.  It shuts down after 10 seconds of the last AVC that arrives.  Unless you are running the browser.

So the problem is with python.

Comment 2 Daniel Walsh 2009-05-06 12:32:26 UTC
Actually there looks like there is a bug, which is preventing setroubleshootd from exiting.  I will fix the bug and it will make setroubleshootd only run when required by an AVC or a user running the GUI.


Fixed in setroubleshootd-2.1.10-1.fc11.x86_64.rpm

Comment 3 Daniel Walsh 2009-05-06 12:44:33 UTC
Also look at

http://illiterat.livejournal.com/4615.html


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