[core-dev] VerifyingFile returns false positivies when checking for file corruptions

I noticed this bug just today, and it seems to be related to the problem that 
I noticed when the ProcessingQueue in the VerifyingFile was not limited in 
size, when I was seeing lots and lots of false positives during corruption 
checking. 

The corrupt chunk was located somewhere in the middle of the file and was 
repeatedly downloaded and found corrupt (~ 30 times) before I restarted 
LimeWire to enable logging for the downloader (which proved to be not helpful 
at all). The same chunk failed TigerTree verification again and again until I 
restarted LimeWire in debugging mode and this time the download just finished 
normally. 

I believe this is happening fairly regularly because I've seen multiple 
downloads going into busy-state at 99% and eventually finishing after a while 
even without restarting LimeWire and I've also seen some Uploaders at 100% 
which were downloading exactly one chunk, then disconnect, reconnect and 
request only one chunk again.

-- 
mfg
gregorio roper
_______________________________________________
core-dev mailing list
[email protected]
http://www.limewire.org/mailman/listinfo/core-dev