After finishing a download of two torrents, both hitting around 1.5MB/s with no high resource usage, and not but a few minutes into seeding, python2.6 (interpreter for deluge) rose to 50% cpu load at 3.0GHz on both of my cores. After consulting someone else using version 1.2.2 who experienced no issues at all, we came to the conclusion that an upgrade of deluge (and required upgrade of the net-libs/rb_libtorrent-0.14.6 dependency) would solve the issue. These two packages are current the highest stable versions available. After upgrading to net-p2p/deluge-1.2.2 (and thus net-libs/rb_libtorrent-0.14.9, both keyword masked on x86), the issue was resolved, leaving deluge seeding the same two torrents at 3-6% (with occasional bursts to ~35%) cpu load at 1.0GHz (ondemand governor). I did not test net-p2p/deluge-1.2.1 however; I simply skipped over to 1.2.2. Not confirmed if it causes the same problem. Also, the problem may lie with net-libs/rb_libtorrent-0.14.6, also unconfirmed. Reproducible: Always Steps to Reproduce: 1. Open one or more torrents in net-p2p/deluge-1.2.0 with net-libs/rb_libtorrent-0.14.6 and begin seeding them. Problems seen also immediately. Actual Results: CPU load increased to ~50% at 3.0GHz and is maintained until the torrents are stopped or the application is closed. Screenshot: http://omploader.org/vM3ljYg Expected Results: Drastically lesser cpu load/frequency (ondemand governor) for simply seeding two torrents. Confirmed by third party and myself once newer version was installed. I'm not sure if anyone else has experienced this. But I sure can reproduce it every time. If reproducible by others, it may be wise to mask 1.2.0 and stabilize version 1.2.2, or 1.2.1 if someone finds it to be in working order. If not, I can just keep 1.2.2 unmasked and stick with it myself. Thanks for any help or comments.
I've also had this problem with deluge-1.2.0 and rb_libtorrent-0.14.6: deluged takes 100% CPU whenever downloading a torrent with the download speed limit turned on. I unmasked and installed net-libs/rb_libtorrent-0.14.9-r1, and that seems to have fixed the problem. For me, deluge isn't the problem, rb_libtorrent is. Solution: stabilise >=net-libs/rb_libtorrent-0.14.9
(In reply to comment #1) Ah, thanks for the comment. I thought it *could* have been rb_libtorrent as well, but didn't confirm since deluge-1.2.2 pulled in a higher version anyway. Good to know though.
Since rb_libtorrent-0.14.9-r1 is already stabilized on x86 and amd64 I am closing this bug. Thanks for reporting the bug in the first place.
