Description of problem: krb5-auth-dialog leaks memory every time it renews a credential - in a long running login session, this can become significant. Version-Release number of selected component (if applicable): 0.6cvs20060212-1.1 How reproducible: Always Steps to Reproduce: 1. Renew credentials repeatedly 2. Watch memory usage grow (Alternatively, attach valgrind and look at the leaked block report) Actual results: Memory is leaked Expected results: No memory is leaked Additional info: I'll attach the patch we're using locally for this issue. I should note that the commit to Gnome CVS which added support for renewable credentials also fixes the problem - so an alternative solution to the patch would be to upgrade the CVS revision in use. Simon.
Created attachment 136793 [details] Fix for creds structure leak
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers
This bug is resolved by the later versions of the package in newer versions of Fedora.