bugmenot2

Since i think version 18429, I have observed a significant memory leak. While the Task Manager reported usage is around 20 MB as before, my actual RAM usage will increase by around a GB while running for about 30-45 minutes. Over longer periods, the usage increases proportionately. When closed, the usage drops almost immediately. I am only seeding about 10 files. This makes it almost impossible to seed for any period of time without constant observation. Running Win7 x64.

The newest version STILL has problems when opening torrent files. If uTorrent isn't currently running when opening a file, all it does is open. You have to open the torrent file AGAIN for uTorrent to add it to the queue. Please, fix the currently reported bugs before adding on new features. Stability and reliability should be held to a higher regard than feature set.

Same problem as Vaxis and bonema. When I upgraded to 18069 more than half of the torrents started seeding for no reason. If I stop them and restart utorrent they begin again (not all of them though). Went back to 17935 for now.

This bug is still present in the newest alpha:

UTP seems totally useless to me, in fact it exhibits symptoms of exactly what it's supposed to solve. That is congestion of my line to a point where it's not usable anymore. I have ~10Mbit/s down- and ~85kB/s upstream, done some testing with utp only, mixed and I am now back at tcp only. I capped my upload to 50kB/s this is the ping statistics to a host I have pretty much exactly 15ms latency to if my line is idle: Approximate round trip times in milli-seconds: Minimum = 41ms, Maximum = 67ms, Average = 52ms Web browsing, SSH to my server etc. is still smooth. With utp this goes in the upper 200-500ms with the occasional spike to 700 and more, even timeouts. Funny thing is: -upload in uT is slow -download in uT is slow And everything else pretty much grinds to a halt. I tried bandwith management on/off, calc_overhead on/off (utp overhead is ridiculous btw if it's displayed correctly), lower settings for connect_speed... nothing helps. So I guess my question is: what's killing my line if it's not the bandwidth (works fine with higher up/down in tcp mode)? I already set a global max. of 120 connections, so unless utp disregards this setting I'm at a loss whats going on here or how this is supposed to be better or if it's just me?

There's still an annoying bug in the latest version that's been reported since the first alpha of 2.1 was released. If you try to open a torrent file when uTorrent isn't currently running, it just opens uTorrent, but doesn't try to download the torrent. You have to open the torrent file AGAIN for uTorrent to recognize what you're trying to do. I hope someone can get on this. Thanks.

How do you do outside seeding on torrent WebUI? I have already a file that I want to upload to a different tracker. It have the same files and so on.