TheShadowRunner Posted July 16, 2006 Report Share Posted July 16, 2006 Hey All, I have this weird problem with uTorrent.First, it seem to happen at random, most of the time the CPU stays at 3-10% alright.But sometimes, like right now, my CPU used is at 60% when NONE OF the processes in the list uses that much!And utorrent seem to use the usual 3-4% too!http://videoff7.free.fr/uto16bug.jpgWhen I close uTorrent, the CPU goes back down to normal, 2-3 when idling.As soon as I re-open uTo, the CPU useage on the status bar says 60%!If i leave uto open and stop all torrents, the problem stays there so it's not a connection issue i guess.If I reclose uTo again. All seem fine again with CPU at 2-3.Very weird. I'm on XP SP2 with latest patches. my Tcpip.dll is patched to 50.Most of the time uTo works just fine though, no abnormal CPU usage.Anyone experiencing the same?Later,TSREdit, just rebooted both computer & modem. All seem to run fine again including uTo and CPU usage.I don't know what triggers this weird CPU behavior but what i do know is that it is linked to uTo for sure and never occured with older built. Also, i don't use a firewall, my router does it and my Antivirus is set to manual. Link to comment Share on other sites More sharing options...
Ultima Posted July 16, 2006 Report Share Posted July 16, 2006 Use Process Explorer instead of Task Manager. Link to comment Share on other sites More sharing options...
TheShadowRunner Posted July 16, 2006 Author Report Share Posted July 16, 2006 Good idea, i installed it.I'll have to wait until the bug occurs again because it has been working fine since i posted my last message on this thread.Later,TSR Link to comment Share on other sites More sharing options...
silverfire Posted July 17, 2006 Report Share Posted July 17, 2006 Use Process Explorer instead of Task Manager.[off-topic]It's a pity that the built in Task Manager shows CPU graphs for dual core more effectively[/off-topic] Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.