I have just installed a clean Wheezy and tried qbittorrent there (the provided v2.4.11) and it runs fine here (CPU usage is normal). This might be caused by a specific torrent or tracker (I remember there used to be a libtorrent bug that would cause high cpu usage with some strange tracker URLs).
Kr, Chris. On Mon, Apr 25, 2011 at 6:20 PM, Christophe Dumez <ch...@qbittorrent.org> wrote: > Have you tried Deluge (also based on libtorrent)? As I said, I suspect > this is a libtorrent issue and not caused by a bug in qBittorrent. > I will install Wheezy in a VM and see if I can reproduce the issue > anyway but please test Deluge to see if you get the same behavior. > > Kr, > Chris. > > On Mon, Apr 25, 2011 at 5:51 PM, Chris Laberti <chrislabe...@gmail.com> wrote: >>> qBittorrent v2.4.11 can be built against either libtorrent v0.14.x or >>> v0.15.x. Both should be fine but some new features are introduced in >>> libtorrent v0.15. Your high CPU problem is likely to be a libtorrent >>> bug though, I would suggest trying a more up-to-date version of >>> libtorrent v0.14 or maybe even v0.15.x. >> >> None of the Debian repositories provide a higher version of 0.14 >> >> Wheezy's 2.4.11 is compiled for 0.14 not 0.15 and it does not work if >> forced to use 0.15. >> >> Experimental's 2.7.2-1 does not work on Squeeze because it requires >> higher versions of at least libssl and libqtcore4. >> >> Please provide a qBittorrent version that works in Wheezy. If not >> possible, please remove qBittorrent in Wheezy since it makes the >> entire system unresponsive due to the 100% CPU. >> >> >> >> > -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
