Hi, i saw today a critical bug...

I have a torrent a 45% with many seeder stucked (it seems the source has not shared it completely to one pear at least and is slow uploading)

I found my download bandwith stuck at 700kB/s, and i wondered how it may happen.

Then i looked on chunk tab of this torrent (i have two other in seed and a global connexion limit to 150).

I saw 116 pear on that single chunk (44) !

But the chunk is a 700kB/s (1MB chunk), but it didn't completed at all even with that full speed of dl (I have a dl bw of 800kB/s).

In fact the chunk looped constantly between 4 and 5 / 64.
(as if each completed section, made cancel the other one in other peer dl).

So i think there is a design bug here, I have no idea where it is in source code, but there is a real problem.

I don't realy care about that problem, fix it by restart the dl did the trick, but it should be fixed asap to avoid any similar problem...

If you need any other info ask i didn't shutdown ktorrent yet.

I hope my info are enough for find the problem.

Did you see anything in the log file like a Hash verification error ?

One possible scenario is that somebody was constantly sending bad stuff, so the chunk had to be redownloaded constantly, but seeing that this bad peer keeps sending bad data, it would fail continuously.

I had some chunk corruption on that torrent, it had been rechecked completely many time.

I have the log, but didn't find "hash verification error" or any of in in 2 last log (1.gz and normal).

May you ask me something more specific ?

I will see if I can reproduce this somehow.