Simeras Posted October 3, 2011 Report Share Posted October 3, 2011 How to reproduce the bug:1. Open Task Manager to monitor CPU usage.2. Find a big torrent, with multiple files in it. At least one of them must be larger than 4GB (important).3. When adding torrent, select no files (Select None) in Download Dialog.4. On files Tab select file (any priority), smaller that 4GB - notice a short spike in CPU usage and no further problems. This step is not important, it just shows, that smaller that 4GB files don't trigger the bug .5. Select a file, which is larger than 4GB - it should trigger the bug. It will download for a short period of time, then "Disk Overloaded" will pop up (without actual HDD usage), download will stop, the file will not be created in download dir., and uTorrent process hangs in processes if you close the program, eating CPU.I checked this with different torrents and different computers (WinXP 32bit, Win7 64bit). Link to comment Share on other sites More sharing options...
Skram0 Posted October 5, 2011 Report Share Posted October 5, 2011 I too have this high CPU usage bug. Also, when I close uTorrent by exiting the program (not minimizing), the process stays running at 100% CPU.I was using v2.2.1 and it worked perfectly. CPU usage while downloading a 12GB file was 1-2%. So I decided to "upgrade" to the latest build yesterday and I get these issues, keeping the same torrent file downloading and no others.So I just installed v2.2.1 back and everything is perfect. Maybe I'll keep trying every release to see if this major bug gets repaired. Because basically v3+ is useless. Link to comment Share on other sites More sharing options...
Firon Posted October 5, 2011 Report Share Posted October 5, 2011 How to reproduce the bug:1. Open Task Manager to monitor CPU usage.2. Find a big torrent, with multiple files in it. At least one of them must be larger than 4GB (important).3. When adding torrent, select no files (Select None) in Download Dialog.4. On files Tab select file (any priority), smaller that 4GB - notice a short spike in CPU usage and no further problems. This step is not important, it just shows, that smaller that 4GB files don't trigger the bug .5. Select a file, which is larger than 4GB - it should trigger the bug.It will download for a short period of time, then "Disk Overloaded" will pop up (without actual HDD usage), download will stop, the file will not be created in download dir., and uTorrent process hangs in processes if you close the program, eating CPU.I checked this with different torrents and different computers (WinXP 32bit, Win7 64bit).Hmm, that's a pretty nasty issue. Link to comment Share on other sites More sharing options...
teamds Posted October 5, 2011 Report Share Posted October 5, 2011 You sir, are my friken HeroI reported it in http://forum.utorrent.com/viewtopic.php?id=103654 as Horder mode.I could not pin it down, but knew it had to do with large torrents that cause it to go into this mode.Once they fix this, I can hopefully upgrade the servers from 2.0.4 - Which has been the most reliable.Karma, beer, whatever cosmic goodies you like for you from me Link to comment Share on other sites More sharing options...
kv3 Posted October 14, 2011 Report Share Posted October 14, 2011 Any word on this? I've had this issue ever since the initial release of 3.0. Running build 25756 on Windows 7 x64. Link to comment Share on other sites More sharing options...
piete Posted October 16, 2011 Report Share Posted October 16, 2011 Bug confirmed. Funny that I managed to download one large file before the bug manifested itself. Link to comment Share on other sites More sharing options...
PHX001 Posted November 27, 2011 Report Share Posted November 27, 2011 This is brilliant. I've been trying to locate the prob and this is definitely it.Leaving this comment so I can track this thread, hopefully some answers arise. Link to comment Share on other sites More sharing options...
Simeras Posted December 12, 2011 Author Report Share Posted December 12, 2011 Was this fixed with 3.1 Stable? Anyone checked?Still using 2.2.1. Seems too much of a hassle to install 3.1 just to revert back to old version if the bug is still there. Link to comment Share on other sites More sharing options...
Firon Posted December 13, 2011 Report Share Posted December 13, 2011 Yes, it's fixed. It was even mentioned in the changelog. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.