Desty

I didn't start using µTorrent for real until build 0.9.1.2 had come out for the Mac which solved the 100% CPU usage problem I'd seen in the previous few betas. But it's been running for a while now, smooth as silk and with extremely low CPU (2-3% when I checked, with 2 torrents downloading and 3 seeding, using DHT and peer exchange) and especially memory (21MB compared to the well over 100MB Azureus was using) usage. So thank you guys! No nonsense, no frills, just a small, fast and powerful BT client which runs on Macs... great stuff

The problem seems to be still present in 0.9.1.2... But when I set a download limit and closed the preferences window, CPU usage dropped to 2.5% or so... bizarrely, it stayed like that, even when I unticked the download limit box!

Annoyingly, a hardware problem forced me to reboot and since then I can't replicate the problem in the same way. Will try this if it appears again though. Not sure what you mean here - I'm not particularly interested in logging blocked packets but it's part of Peerguardian which seems to work quite well in general. At least it doesn't hang my Mac anymore...

No; 0.9.1.1 was my first ever install of uTorrent and it goes to 100% as soon as the program loads (with no torrents) and stays that way until I quit. All the settings are the default for a new install, which don't have upload/download limits. I've installed 0.9.0.4 as a workaround and that seems fine for now. I also noticed that when the bug hit, pplogger (associated with the PeerGuardian anti-p2p/spyware firewall) maxed out as well until I killed it. I'm not quite sure what that implies except that a lot of requests are going through the network stack... [edit] ... but disabling DHT and Peer Exchange on 0.9.1.1 make no difference here.