behavior after disk overload

[icebox]

I understand why disk overloads happen, but what I don't understand is why, nearly all the time, after there has been a 100% disk overload, even if all torrents are stopped, the program never leaves overload mode and acts as if there is still a 100% disk overload. I'm using build 30003 of 3.3.1, on windows 7.

Second, after closing the app, utorrent remains in memory, consuming the same memory footprint and using about 2 to 3% of cpu. A different thread suggested that it was communicating with trackers of active torrents, and when done it will shut itself down. But I stopped all my torrents before closing the program, and I don't see what it has to communicate at this point.

Thanks

[ciaobaby]

even if all torrents are stopped, the program never leaves overload mode and acts as if there is still a 100% disk overload

Because it takes time for the disk queue to empty and/or drop below the queue depth that uTorrent 'regards' as safe.

[icebox]

How long should it take? Because I've let it sit several hours with no activity and the 100% message doesn't change.

[ciaobaby]

Twice as long as it is from one end to the middle!

You're the only one who can determine that for your system.