Hi Devs!
Found another bug (but iirc it's present since a long time):
If a file is downloaded very fast (in my case, that's 100+k), aMule will crash as soon as it is finished and ready to be hashed for completion. It doesn't matter if this file is downloaded from 1 or more sources at the same time. If you restart aMule after the crash, it checks the file and immediately marks it as completed.
My guess is, that the crash is due to a buffer overflow or something alike which doesn't happen on slow recieves (like trying to write over the border of the file).
I'm using a binary release of aMule so I can't give you a gdb backtrace, sorry. I hope I could specify the bug so you can locate the problem
Bye!
