Hide Forgot
Description of problem: Over time the machine gets slow and bogged down. Many processes leak core and have to be restarted (firefox, thunderbird, nautilus). This process is one of the top ten big ones. Version-Release number of selected component (if applicable): rpm -q -f /usr/lib/python2.6/site-packages/rabbitvcs/services/checkers/loopedchecker.pyc rabbitvcs-core-0.13.3-1.fc13.noarch How reproducible: yes Steps to Reproduce: 1. login to gnome in 2010-12 2. use nautilus to move around vast and trivial directories 3. nautilus comes and goes (crashes) 4. rabbitvcs is in the background 5. observe the size of rabbitvcs Actual results: See 500MB Expected results: A lot less than that. ~100MB seems to be a going rate for "helper" processes. Additional info: See process 21153 $ ps -lef | sort -n -k 10 | tail -n 6 0 S wbaker 22568 1 0 80 0 - 99165 poll_s 07:52 ? 00:00:26 xsane 0 S wbaker 22013 1 0 80 0 - 99985 poll_s Jan16 ? 00:34:47 gedit 0 S wbaker 21153 21152 0 80 0 - 141992 pipe_w Jan03 ? 00:00:43 /usr/bin/python /usr/lib/python2.6/site-packages/rabbitvcs/services/checkers/loopedchecker.pyc 0 S wbaker 9673 22073 0 80 0 - 147914 poll_s Feb02 ? 00:12:55 nautilus --sm-client-id 1010eaf64f6a8dd0f9128356862072663400000265000049 --sm-client-state-file /home/wbaker/.config/session-state/nautilus-1288011599.state 0 S wbaker 28342 28324 25 80 0 - 218295 poll_s 09:05 ? 00:08:41 /usr/lib/firefox-3.6/firefox 0 S wbaker 21331 21327 6 80 0 - 290499 poll_s 07:43 ? 00:07:42 /usr/lib/thunderbird-3.1/thunderbird-bin $ bc scale=6 141992*4096/1024^3 .541656 SZ= ~550MB I am unclear if I can just "kill & restart" this process. That would be a fine remediation here. The python code says ... """ Convenience script for performing status checks in a separate process. This script is NOT meant to be run from the command line - the results are sent over stdout as a byte stream (ie. the pickled results of the status check). """ I wish to be able to remediate this memory leak without logging out.
Created attachment 477259 [details] The error message ... as seen
Hey Wendell, I just updated RabbitVCS's packages to 0.14.1.1 (As of this writing they haven't landed on updates-testing on f14 yet, but it shouldn't be long until they do). [1] Large Memory Usage, reported here[2] hasn't been fixed, but one of the side effects, Nautilus lockups, has. Speed's also greatly improved in 0.14.1.1 (I've been using it for several weeks now). I'd love it if you helped me test these packages. Thanks! [1] https://admin.fedoraproject.org/updates/rabbitvcs-0.14.1.1-1.fc14 [2] https://code.google.com/p/rabbitvcs/issues/detail?id=90
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.