Jump to content

Download speed throttling causes UI lag, client freezes


Recommended Posts



My internet speed is 3 MB/s (25 Mbit/s)

If I try to limit uTorrent to 2500 kb/s so I can use 500 kb/s myself, strange behavior starts:

  • 100% CPU usage (Seeing it as 28% on my quad core, which is 100% of one core and 3% of a second core which I guess uTorrent's other threads are using.)
  • The UI becomes unresponsive, updating at about 0.1 FPS instead of 60.
  • Torrents also seem to download much slower during this problem.
  • But uTorrent reports false speeds like 80 MB/s, when my internet is not even capable of such speeds.

Unplugging the net cable and waiting about 1 minute so the client can catch up will eventually fix the UI lag.

I don't like force killing the executable as that causes all my torrents to re-verify and then just stop (so I need to manually restart them all.)

Turning off download speed throttling will also avoid the problem but then I can't watch YouTube videos seamlessly.


Strangely, upload speed throttling is unaffected.

This issue started 2 or 3 versions ago.



Daniel "3ICE" Berezvai

Link to comment
Share on other sites



No, of course not. I apologize.

Unfortunately I cannot pinpoint the exact time the issue started, as I usually pay no attention to software that just works flawlessly. Like uTorrent (...used to, until now)

"2 or 3 versions ago" is the best approximation I can give.


But let's see:




I posted on "06 Jul 2014", just after updating to 3.4.2 (build 32080) and seeing my issue was still unresolved.

Like the majority of people, I always use public stable builds, and auto update is enabled, but not the beta channel.


The versions prior to 3.4.2 are:

2014-06-19: Version 3.4.2 (build 32080)
2014-06-12: Version 3.4.2 (build 31743)
2014-05-29: Version 3.4.2 (build 31515)
2014-05-23: Version 3.4.1 (build 31395)
Therefore I'd wager my issue started with build 31515 or 31743, making 31395 the last well-working version for me.
Daniel "3ICE" Berezvai
Link to comment
Share on other sites



So far so good; The issue hasn't reared its ugly head since updating to 32257.


Will keep my eyes open,



p.s.: Why is the smaller build number 32247 dated 2014-07-05 and build 32257 dated 2014-07-04 - the day prior? The larger build number came out before the smaller. Shouldn't they be the other way around?

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...