Bug 597669
Summary: | Memory leak in krb5-auth-dialog when ticket renewal is not acted upon for a while | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bojan Smojver <bojan> |
Component: | krb5-auth-dialog | Assignee: | Itamar Reis Peixoto <itamar> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 13 | CC: | amigadave, helge.deller, itamar, ktdreyer, peter.engel |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | krb5-auth-dialog-0.16-1.fc14 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-06-27 17:03:46 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
Bojan Smojver
2010-05-30 02:49:37 UTC
Left it overnight again. Ticket expired and I now have krb5-auth-dialog using 153 MB of RES memory. Actually, make that 154 - I just allocated another MB. Yep, in just a few minutes it went from 10 MB RES to 36 MB RES on ticket expiry. It happened again, up to 61 MB RES after ticket expired. The time between ticket expiry and renewal is important. The more time passes, the bigger the memory leak. This has been fixed upstream. Could you please have a look at the bug report there and apply the fix. Can we please get 0.16 in F-13 as well, now that it's been released? Anyone? Tested overnight with an expired ticket and ss far as I can see, leaks have been fixed here: http://koji.fedoraproject.org/koji/buildinfo?buildID=183791 Please push to updates. I've been using the above Koji build of 0.16 for a while. It is working well, and I see no obvious memory leaks. Please push this (or 0.17, released today) to updates. Ping... it's been a month since my last comment. Any word on this? 0.16.2 release (rebuilt on my own for F-11) is working here fine as well. Please push to updates. IMHO it's important to get this fixed. (In reply to comment #10) > 0.16.2 release (rebuilt on my own for F-11) is working here fine as well. > Please push to updates. IMHO it's important to get this fixed. Yes, please push to updates. Without the update, this thing eats memory like there is no tomorrow. 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. This was eventually fixed in Fedora 14, with the first release of 0.16. |