Bug 602485
Summary: | packagekitd leak - cause OOM killer | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mads Kiilerich <mads> | ||||
Component: | PackageKit | Assignee: | Richard Hughes <richard> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 13 | CC: | jonathan, rhughes, richard, smparrish | ||||
Target Milestone: | --- | Keywords: | Reopened | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-06-27 17:55:18 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: | |||||||
Attachments: |
|
Description
Mads Kiilerich
2010-06-09 23:15:38 UTC
Hmm, are you able to get the full data from valgrind when this happens please? That looks like a pretty huge leak, more than can be accounted from those sqlite databases on their own. Sorry, it only happened once and I don't know how to reproduce it, so I don't think I can provide further information. Valgrinding such a python system service would be another hard challenge. (I can imagine that systemtap could be more useful, but now it's too late ...) Please just take this as a strong evidence that something strange happened. Perhaps it together with other strange reports will show some kind of pattern later on. That might be all we can do ... Please close this issue or leave it open, whatever you prefer. Okay, thanks for reporting, and please re-open if it happens again. Created attachment 431576 [details]
peek into /proc for packagekitd
It haven't crashed yet, but top shows packagekitd in bad company of memory hogs:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1924 mk 20 0 1835m 714m 9896 S 9.1 35.5 653:15.06 firefox
17107 mk 20 0 1124m 335m 4088 S 3.0 16.7 163:34.33 eclipse
2330 root 20 0 1927m 196m 2096 S 0.0 9.8 5:51.06 packagekitd
5867 mk 20 0 738m 88m 6976 S 1.3 4.4 70:05.93 thunderbird-bin
lrwxrwxrwx 1 root root 0 Jul 13 21:28 /proc/2330/exe -> /usr/sbin/packagekitd (deleted)
So again bad things happens when packagekit is upgraded (and the user has more important things to do than restarting).
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |