- downloading a torrent with only one utorrent 1.5.0.0 seeder
- DHT disabled in preferences
- encryption enabled but ip-adress doesn't show the encryption icon

After some time (few minutes or less) downloading at 8-16KB/s the torrent gets stalled. When stopping & restarting the torrent the same result, first a decent download speed for one peer, then drops to 0KB instantly.

If others (with updated svn) notice the same behaviour with one seeder in swarm, be it utorrent or another client, then please poke this thread.

Should be fixed now.

After some time (few minutes or less) downloading at 8-16KB/s the torrent gets stalled. When stopping & restarting the torrent the same result, first a decent download speed for one peer, then drops to 0KB instantly.

If others (with updated svn) notice the same behaviour with one seeder in swarm, be it utorrent or another client, then please poke this thread.

I noticed the same problem. I don't think this is the problem with the hash verification error. I just tried the last revision 535711.
It is occured when only one seeder is available, no leachers and is connected on low speed (1 or 2 KB).
When the timeout expire, the seeder becomes "snubbed" and it seems that ktorrent doesn't reattempt the connect to it again, so the torrent become stalled. When I stop/start torrent, ktorrent reattempt connection, so the download start again for few minutes, the torrent stalled and seeder become snubbed.

It seems that when a seeder (peer) once become snubbed, no future connection is established with the same seeder (peer).

Nikolay wrote:I noticed the same problem. I don't think this is the problem with the hash verification error. I just tried the last revision 535711.

I've the problem still here too.

When the timeout expire, the seeder becomes "snubbed" and it seems that ktorrent doesn't reattempt the connect to it again, so the torrent become stalled. When I stop/start torrent, ktorrent reattempt connection, so the download start again for few minutes, the torrent stalled and seeder become snubbed.

Yeah, snubbed flag seems to get activated after two minutes of stalled on the peer.

It seems that when a seeder (peer) once become snubbed, no future connection is established with the same seeder (peer).

Looks the same here.
Now trying with an azureus 2.4.0.2 seeder...

EDIT
Same thing with azureus.
Now trying with both the azureus and utorrent seeder...

EDIT
Same thing with two seeders and no leechers.
Would be nice to monitor this with ethereal, good chance for me to learn this program.

Yeah, I've got a few stalled torrents too. In my case there are lots of seeders and leechers too. Seeders get me snubbed after some time. Leechers keep sending a bit more and then they snub me too.
Stop/Start torrent makes it continue properly.

I was kinda hoping that the recent changes will fix this

If i understand ethereal right, the seeder sends constantly twice the same package after some time.

PS.Seeding to only one peer in swarm also looks hard at the moment.

This problem might be linked to the stalled in general. Leeching with only one or two peers this bug is still present here.
I have no clue at the moment, but if there's anything in ethereal i can look for, just poke me.

svn 538719

We are still working on this. For some reason KT stops sending requests to a peer which eventually snubs us.

We're working on it, the planned beta release will be shifted until this bug is fixed.

UPDATE: It seems we have a working fix, this is only symptom treatment, it doesn't address the root cause of the problem.

George wrote:We're working on it, the planned beta release will be shifted until this bug is fixed.

(i am sorry, i was sort of in panicmode)

UPDATE: It seems we have a working fix, this is only symptom treatment, it doesn't address the root cause of the problem.

Is this the

Code: Select all

Weird bug detected !
Making sure everything is back OK

in logviewer?

Yeah, that's it

It seems to help, but the real cause of the problem is still unsolved. We're hoping that it will be, soon enough.