100% CPU problem still exists on 1.3.2 and 1.3.3

General support for problems installing or using Deluge
Post Reply
Bob E

100% CPU problem still exists on 1.3.2 and 1.3.3

Post by Bob E »

After installing 1.3.0, I encountered the 100% CPU issue. I found the thread on this forum about this, and that starting with 1.3.1 is was fixed. Unfortunately, not so.

OK, nuts and bolts first: I tried this on 3 different computers, one desktop running Linux Mint 10 64bit, AMD Athlon 64 X2, another desktop with Mint 10 32bit, AMD Athlon 64 (single core), and an 8 year old Dell Inspiron 5100 laptop with Ubuntu 10 10, Intel ???.

On all three machines, I tested Deluge 1.3.2 and 1.3.3.

The way I found the problem originally was this: while downloading, on the Deluge menu bar, I clicked "Help", then clicked "Home". CPU ramped up to 100%. Closed the browser that it opened, no change...had to close Deluge. Restarted Deluge, all is calm, CPU running at 10% +/-. Then, thinking the browser triggered this, I opened Firefox while Deluge was running normally. No change to CPU other than starting FF. Surfed a little bit, no issues. Then tried it with Chrome...no trouble. Went back to Deluge Help menu, clicked "Community", WHAM! 100% CPU. I also changed default browsers to see if one or the other was the cause when clicking on the Help links, and it still went to 100% with both Firefox and Chrome. Next, I tried it all over again, this time without an active torrent download, and it still occurs.

So, it seems the web links in the Help menu are triggering this problem. It happened for me on all three machines with 1.3.2 and 1.3.3.

Now, my user solution is that I just don't click those links again. (Don't need to anymore...I know where you're at. ;) ) But I'm sure a new user, who doesn't watch or care about monitoring system functions, would click on one of those links and not know their computer just went into maximum core processing and could damage their system.

I like Deluge a lot. Compared to all other choices for Linux, this one is the best! So, I don't know if this info has been helpful or not, but if I missed something that you might want to know, let me know and I can hopefully post some answers.
Cas
Top Bloke
Top Bloke
Posts: 3681
Joined: Mon Dec 07, 2009 6:04 am
Location: Scotland

Re: 100% CPU problem still exists on 1.3.2 and 1.3.3

Post by Cas »

If you had actually read the posts or tickets you would have seen that it has nothing to do with deluge but instead its a pygtk issue, so you need to update your OS to a fixed version or patch pygtk with the fix yourself.
Bob E

Re: 100% CPU problem still exists on 1.3.2 and 1.3.3

Post by Bob E »

You're awful quick to blame everyone else for the problem. Well, if any of your "patches" actually worked, I would not have bothered to post in the first place. In addition, it's interesting that of the top bittorrent clients for Linux, yours is the only one that suffers from this problem.

Well, I stand corrected, Deluge is not the best available client.
Cas
Top Bloke
Top Bloke
Posts: 3681
Joined: Mon Dec 07, 2009 6:04 am
Location: Scotland

Re: 100% CPU problem still exists on 1.3.2 and 1.3.3

Post by Cas »

You're awful quick to blame everyone else for the problem.
To put it simply, it is impossible for this to be a Deluge issue as you are describing exactly the symptoms of the well known pygtk bug, whereby opening an external application causes high cpu usage.

I personally made sure the patch was backported to Natty and Maverick, via SRU, so that Ubuntu Deluge users would no longer encounter this issue. Plus since I run Ubuntu Natty I would notice if there was any regression of this bug.

http://dev.deluge-torrent.org/ticket/1396
https://bugs.launchpad.net/ubuntu/+sour ... bug/664920
In addition, it's interesting that of the top bittorrent clients for Linux, yours is the only one that suffers from this problem.
Unless they are using pygtk for the interface they cannot encounter the same problem.
Post Reply