Limewire 4.2.3 Gets Lost

[trap_jaw4]

Originally posted by JayG
Kind of sounds like the LRC check, etc., on segments is not being properly done while the download is in progress. Whatever the cause, the process that recovers from that problem needs to learn not to hog all the processing time.

Yes, that was my mistake, I didn't want to rely on TigerTree hashes during the download and do the TigerTree hashes only if LimeWire detected a corruption. But I must admit, it was not a good idea at all. There is a patch for that problem but it did not make it into LimeWire 4.2. You may expect that to be fixed in one of the 4.3 betas.