rtorrent-0.8.9(and 0.8.7-r4) with curl-7.24.0 leads to 100% cpu usage. With previous stable curl-7.21.4 this behaviour not observed. Reproducible: Always Steps to Reproduce: 1. emerge -avq1 =net-misc/curl-7.24.0 rtorrent 2. run rtorrent $list_of_more_than_500_torrent_files Actual Results: 100% of cpu load an average of. Expected Results: About 1-5% of cpu load an average of. Tested on Hardened Gentoo. On Common Gentoo system with list of 1 torrent file this behaviour not observed.
I confirm that. Using ~amd64. Downgraded to curl-7.21.4.
The same for me. (~amd64) works fine with net-misc/curl-7.23.1
Works on my amd64 (stable) server. What are your versions and USE-flags? I have: [I] net-misc/curl Available versions: 7.21.4 ~7.21.6 ~7.21.7 ~7.21.7-r2 ~7.22.0 ~7.23.1 7.24.0 ~7.25.0 {ares gnutls idn ipv6 kerberos ldap nss ssh ssl static-libs test threads} Installed versions: 7.24.0(22:54:52 01/27/12)(gnutls idn ipv6 ssl threads -ares -kerberos -ldap -nss -ssh -static-libs -test) [U] net-libs/libtorrent Available versions: 0.12.5 0.12.6 (~)0.12.7 (~)0.12.7-r1 (~)0.12.8[1] 0.12.9!t (~)0.13.0 {debug ipv6 ssl test} Installed versions: 0.12.9!t(14:59:55 12/10/11)(ssl -debug -ipv6 -test) [U] net-p2p/rtorrent Available versions: 0.8.6-r1 (~)0.8.6-r4 (~)0.8.7-r3[1] (~)0.8.7-r4 (~)0.8.8[1] 0.8.9!t (~)0.8.9!t[1] (~)0.9.0 {color daemon debug ipfilter ipv6 test xmlrpc} Installed versions: 0.8.9!t[1](15:42:34 12/10/11)(color ipfilter xmlrpc -daemon -debug -ipv6 -test)
I tried with the above listed USE flags and versions, and I still suffer from the 100% CPU problem. Machine is an AMD64 SMP. Downgrading to curl-7.21.4 makes the problem go away.
With the release of curl-7.25.0-r1 situation has not changed, rtorrent also loads cpu at 100%.
I confirm - the problem is exists. Downgrade curl from 7.24.0 to 7.21.4 solves the issue.
Created attachment 310273 [details] Valgrind curl-7.21.4
Created attachment 310275 [details] Valgrind curl-7.24.0
Perhaps Valgrind results have useful information. http://backbone.ws/trash/curl-7.21.4.out http://backbone.ws/trash/curl-7.24.0.out http://backbone.ws/trash/rtorrent-0.8.9_curl-7.21.4.out http://backbone.ws/trash/rtorrent-0.8.9_curl-7.24.0.out
I don't observe this problem for several months. There are suspicions that the problem was neither in rtorrent, nor in curl, but somewhere at lower level. If no one else is watching this bug, perhaps it should be marked as "RESOLVED-> FIXED".
