Bug 608438 - deluge eats 100% CPU after opening the Downloadfolder via GUI
deluge eats 100% CPU after opening the Downloadfolder via GUI
Product: Fedora
Classification: Fedora
Component: deluge (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Rahul Sundaram
Fedora Extras Quality Assurance
: 667295 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2010-06-27 10:27 EDT by Stefan Jensen
Modified: 2011-06-27 15:00 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-27 15:00:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stefan Jensen 2010-06-27 10:27:55 EDT
Description of problem:

Deluge starts to eat 100% CPU after i right click on "open folder" for a downloaded torrent.

Version-Release number of selected component (if applicable):

$rpm -qa| grep deluge


How reproducible:


Steps to Reproduce:

1. download a torrent
2. within deluge, right click on a torrent and select "open folder"
3. watch cpu load going to 100%
Actual results:

100% cpu load

Expected results:

no such cpu load

Additional info:

even when the folder is closed after that, cpu load stays that high forever.
Comment 1 Fedora Admin XMLRPC Client 2011-03-16 04:13:54 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 2 Rahul Sundaram 2011-03-16 11:49:40 EDT
*** Bug 667295 has been marked as a duplicate of this bug. ***
Comment 3 Fedora Update System 2011-03-16 14:54:38 EDT
deluge-1.3.1-2.fc14 has been submitted as an update for Fedora 14.
Comment 4 Stefan Jensen 2011-03-20 09:09:44 EDT
Doesn't work for me. Deluge still eats full cpu after opening a download-folder.

$rpm -qa| grep deluge

Comment 5 Rahul Sundaram 2011-03-20 11:51:38 EDT
Not reproducible for me.  Would you mind reporting this upstream directly?

Comment 6 Bug Zapper 2011-06-01 11:28:20 EDT
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: 
Comment 7 Bug Zapper 2011-06-27 15:00:28 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.