Bug 204274

Summary:	apparent memory leak in setroubleshootd
Product:	[Fedora] Fedora	Reporter:	Valdis Kletnieks <valdis.kletnieks>
Component:	setroubleshoot	Assignee:	John Dennis <jdennis>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	dmalcolm, oliva
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	0.49	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-10-03 16:19:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Valdis Kletnieks 2006-08-28 05:06:57 UTC

Description of problem:
ps aux reports:

root      2424  2.1 52.6 1525452 407836 ?      Ssl  Aug27  11:42 /usr/bin/python
/usr/sbin/setroubleshootd

Disk light was on solid because system was thrashing - an 'su' to kill it took
over 2 minutes from hitting 'enter' to the Password: prompt. So no extensive
debugging was possible.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 John Dennis 2006-09-07 20:08:47 UTC

A very likely cause of memory leaks is our current use of libxml2. Unlike most
python object memory references are not automatically freed in libxml2. Once a
document is created it must be explicitly freed with doc.freeDoc() and xpath
contexts must be freed with ctxt.xpathFreeContext(). We create quite a few
documents (DOM trees) and search contexts, but we never explicitly free them. We
need to add these calls.

Comment 2 John Dennis 2006-09-07 20:10:43 UTC

*** Bug 205245 has been marked as a duplicate of this bug. ***

Comment 3 John Dennis 2006-10-03 16:19:22 UTC

This should be fixed in the current code base, we now free all libxml2 documents
and xpath contexts.