High CPU usage on 1.3.0_rc1

[cca]

OK, with this I am confirming there is a bug in libtorrent 1.5.3, just hit the bug with Deluge 1.2.3. Common denominator seems to be torrents with very high number of seeder/leechers. Will attempt to fallback to 1.5.1 and test.

[abubin]

i am testing 1.3.0 with libtorrent 1.5.2 now. Seems to be quite stable with moderate CPU load.

Before this I have tried 1.3.0 with libtorrent 1.5.3 and it crashes.

At first 1.3.0 with libtorrent 1.5.2 also crashes. But it is gone after I deleted the whole deluge config folder and redo me configurations. Will report back if load starts to go high again.

[durilka]

I'm on the normal desktop 2core Intel having close issue. After some time cpu usage goes 100% but also all my memory gets consumed by the deluge. version is 1.3.0-0ubuntu1. attachments are disabled here, so short peek into last lines of debug log.
It actually goes like this for about 1.5 million lines (and to me looks like deluge chokes on sending announces and never really receiving them, even though net is up):

Code: Select all

[DEBUG   ] 23:25:40 alertmanager:123 tracker_error_alert: <<file#1>> (<<tracker#2>>) (-1) Connection timed out (56)
[DEBUG   ] 23:25:40 torrentmanager:896 on_alert_tracker_error
[DEBUG   ] 23:25:40 alertmanager:123 tracker_announce_alert: <<file#1>> (udp://<<tracker#1:80>>) sending announce (started)
[DEBUG   ] 23:25:40 torrentmanager:876 on_alert_tracker_announce
[DEBUG   ] 23:25:40 alertmanager:123 tracker_announce_alert: <<file#1>> (http://<<tracker#1>>) sending announce (started)
[DEBUG   ] 23:25:40 torrentmanager:876 on_alert_tracker_announce
[DEBUG   ] 23:25:40 alertmanager:123 tracker_announce_alert: <<file#1>> (udp://<<tracker#2:80>>) sending announce (started)
[DEBUG   ] 23:25:40 torrentmanager:876 on_alert_tracker_announce
[DEBUG   ] 23:25:40 alertmanager:123 tracker_announce_alert: <<file#1>> (<<tracker#2>>) sending announce (started)
[DEBUG   ] 23:25:40 torrentmanager:876 on_alert_tracker_announce
[DEBUG   ] 23:25:40 alertmanager:123 tracker_error_alert: <<file#1>> (http://<<tracker#1>>) (-1) Connection timed out (83)
[DEBUG   ] 23:25:40 torrentmanager:896 on_alert_tracker_error
[DEBUG   ] 23:25:40 alertmanager:123 tracker_announce_alert: <<file#1>> (udp://<<tracker#1:80>>) sending announce (started)
[DEBUG   ] 23:25:40 torrentmanager:876 on_alert_tracker_announce
[DEBUG   ] 23:25:40 alertmanager:123 tracker_announce_alert: <<file#1>> (http://<<tracker#1>>) sending announce (started)
[DEBUG   ] 23:25:40 torrentmanager:876 on_alert_tracker_announce
[DEBUG   ] 23:25:40 alertmanager:123 tracker_announce_alert: <<file#1>> (udp://<<tracker#2:80>>) sending announce (started)
[DEBUG   ] 23:25:40 torrentmanager:876 on_alert_tracker_announce
[DEBUG   ] 23:25:40 alertmanager:123 tracker_announce_alert: <<file#1>> (<<tracker#2>>) sending announce (started)
[DEBUG   ] 23:25:40 torrentmanager:876 on_alert_tracker_announce

[johnnyg]

That looks like the bug in libtorrent 0.15.3. Is that the version of libtorrent you are using?

[skolima]

On deluge 1.3.0 and rb_libtorrent 0.15.1 today I hit 100% cpu usage during download, although this did not happen before. I'll check rb_libtorrent 0.15.4.

[skolima]

Using deluge 1.3.0 and rb_libtorrent 0.15.4 this bug still manifests, I'm checking deluge 1.3.1 (which is supposed to fix the web-interface 100% CPU usage bug) right now and things seem to be much better.