Bug 80353
Summary: | Probable memory leaks in anaconda | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | jfm2 |
Component: | anaconda | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED RAWHIDE | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | phoebe | CC: | wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-01-24 22:41:20 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
jfm2
2002-12-24 22:11:17 UTC
There were some leaks in the version of pygtk2 used in phoebe. 1.99.14 fixes these this seems to be fixed In Phoebe2 by the end of installation it was using some 350 megs of memory+swap (I installed less things than when I opened the bug). Checks during the installation showed constant increase during package installation phase The output of free (or contents of /proc/meminfo) can be misleading. How the kernel manages physical resources like memory and swap space is separate from how anaconda (or any other userland process) manages the memory allocated to it by the kernel. The best indication of anaconda's memory use is /proc/$PID/status, where $PID is the pid of anaconda. I have run some additional tests and anaconda does not appear to be leaking memory in Phoebe public beta 2. Usually when anaconda does have a memory leak (and I think there was a minor one in Phoebe public beta 1), I will see a few of my testcases stall out completely, particularly some of the low-memory testcases. I did not see this with the second public beta. Re-closing this bug. |