stoeptegel wrote:Chunk xxx downloaded message? Nope.
Though, the swarm only has 100% completed peers so it probably only has good chunks.

No something along the lines of
Hash verifcation error
is : <some-hash>
should be : <another-hash>

The hashes are random strings of numbers and letters.

Nope that message wasn't there. KTorrent downloaded(after a restart) but the % and chunk part idled on the same number, and after a while in stopped downloading while there where still peers assigned.

I tried it like 5 times, and had the same finding everytime.

Got another stalled torrent. (this time on 41%)

- restarting the torrent makes no difference
- the chunk assignment list immediately comes back in KTorrent + "Loading 44 active chunk downloads" in -debug after restarting the torrent
- restarting KTorrent seems to work
- nothing strange in log (i have saved it though)

Because KTorrent downloads fine again after a restart (and the chunk assigment gets lost when doing that), i think it could have something todo with or arround the assignments. Just a guess though.

even if I didn't have a stalled torrent for weeks (crossing fingers !!!) I noticed in several instances, when I was around to monitor a finishing torrent, that the last (say 5 to 10) chunks seem to download much slower than the ones before

this morning I had a finishing torrent (5 seeds and 20+ leechers) and the last 5 chunks were "downloading", each one assigned to 1 client, speed mostly 0.0 with an occasional 0.2 KB peak... I stopped KTorrent and restarted it, and in a matter of seconds I had all 5 chunks running full speed with several clients assigned to each

It looks like the stalling occurs in a gradual way, things slowing down more and more until either the last chunk eventually loads or the torrent is stalled forever

this morning I had a finishing torrent (5 seeds and 20+ leechers) and the last 5 chunks were "downloading", each one assigned to 1 client, speed mostly 0.0 with an occasional 0.2 KB peak... I stopped KTorrent and restarted it, and in a matter of seconds I had all 5 chunks running full speed with several clients assigned to each

We distribute all peers we can assign over all the chunks. And this happens at the restart, but not at the end of a long period of downloading. Strange ...

I need a way to trigger this bug.

I'm yet to download a torrent 1GB or larger without this happening, so surely it isn't too hard to trigger it, although it would be expensive in terms of bandwidth. :-/

I just wanted to add that I'm in the same boat with the 99.9% problem. I'm running OpenSUSE 10.0, Ktorrent 1.2, and have had this problem with multi- and single-file torrents around 20% of the time. I never knew that all I need to do is shut down Ktorrent and start it back up - I used to rename the torrent, and just redownload the stalled section (in the case of a large single file, I'd load up the stock Bittorrent software). Thanks for the workaround. I just finished downloading a file that's been hanging at 99.9% all night.

Baltika

I've found a torrent that has stopped at around 99% three times now. I've deleted it and tried it again each time. I can turn off Ktorrent, restart it, and it'll download the last remaining 5 meg or so, but continue this cycle endlessly.

BaltikaTroika wrote:I've found a torrent that has stopped at around 99% three times now. I've deleted it and tried it again each time. I can turn off Ktorrent, restart it, and it'll download the last remaining 5 meg or so, but continue this cycle endlessly.

Can you send that torrent to me for testing ?

BaltikaTroika wrote:I've found a torrent that has stopped at around 99% three times now. I've deleted it and tried it again each time. I can turn off Ktorrent, restart it, and it'll download the last remaining 5 meg or so, but continue this cycle endlessly.

are you sure it's not an invalid data from the seeder (i.e. are there other peers that complete or are they all stalled at 99% ?)

I saw this happen once, where 20 leechers were waiting for the last two chunks and the only seeder kept sending erroneous chunks that were rejected, so the seeder was banned until restarting KT and the cycle repeated endlessly...

I'll just like to confirm that this problem is for real. I'm downloading a torrent from Mandriva that consists of four files, one iso(DVD) one md5 a sha1 and one idx and it stalled! Stopping starting has no effect. Ending the program does not help.
I'll be happy to mail torrent file if someone want to test. I'm using version 1.2 with kde 3.5.2 on FreeBSD stable 6.0.
/Leslie

I stopped and started the torrent no change. Then I shut down the program. Now it has started downloading but from scratch!!!!! 4.2 Gb just got deleted and I don't know how (
/Leslie

I have to report this as well. Sometimes KT stalls at 99% with no obvious reason. I mean there are seeders and all went well until 99%. Last case was with approx 50 seeders and average speed above 1MiB/s. Restarting KT causes all stalled 99% torrents to finish immediately (as long as there are seeders).

Svn At revision 530499.

I had the same problem today with the version of ktorrent in the latest Dapper repository. Attempted to download a 1.28 gigabyte file, waited for two days for it to finish --- only to have it get stuck at 99.90% complete. Stopped and restarted ktorrent over and over again, waited for 8 hours in the last attempt, last chunk simply never downloaded.

Finally gave up and imported the mostly-downloaded file into azureus --- which grabbed the last chunk right away, no problems.

syntheticzero wrote:I had the same problem today with the version of ktorrent in the latest Dapper repository. Attempted to download a 1.28 gigabyte file, waited for two days for it to finish --- only to have it get stuck at 99.90% complete. Stopped and restarted ktorrent over and over again, waited for 8 hours in the last attempt, last chunk simply never downloaded.

Finally gave up and imported the mostly-downloaded file into azureus --- which grabbed the last chunk right away, no problems.

Euhm this is fixed