Description of problem: After running for a few days the program grows from about 100 MB when started, up to several hundred MB to a few GB. I constantly have to kill and restart it every few days to free up memory. Version-Release number of selected component (if applicable): blueproximity-1.2.5-6.fc13.noarch How reproducible: Always. I only noticed this recently, so it might have something to do with the recent change made, from the rpm changelog: Sun Jun 06 2010: Add patch for python ConfigObj changes.
I've never ran it more then a day so I've not ran into this issue. I don't suspect http://cvs.fedoraproject.org/viewvc/F-13/blueproximity/blueproximity-python-ConfigObj.patch?revision=1.1&view=markup would cause a memory leak. It's the recommended action for ConfigObj 4.7.0 when dealing with legacy code: http://www.voidspace.org.uk/python/configobj.html#configobj-specifications There are actually a lot of things I'd like to change about this software. Seeing as how the last release was 2008-02-28 it's likely going to need to be whipped into shape very soon. I don't particularly like the way this is written, but I've not allocated any time to re-write it. If you could get me some debug information on what the python stack is doing when you are seeing this much memory being used, it'd give me a starting point.
Hi Jonathan, The patch was just a guess since it was only recently that I noticed the memory growing and I have been using it for at least a year or more, with my desktop login session often lasting several days or more. What kind of debugging info do you want, just a gdb stack trace, or some other python debugging info? I don't know much about python, so instructions would help. I see the memory grow from initial start, at a fairly steady rate of about 140kB/min. I forgot to include it before, just in case it matters, but I am on a x86_64 F13 system. Thanks, ~Jason
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.