Hi,
i've been playing with aMule for a time, and recently discovered that aMule can be accidentally crashed by the user following those steps:
1.- When connected to a server, go to the Search button.
2.- Write whatever you want into the search field (i.e. "x files", "english" "soundtrack")
3.- Fill the "min size" field (i.e. 600)
4.- Start the search.
5.- When it finishes, select the content of "min size" (the "300" value) field and try to overwrite it.
I observed that when aMule crashes by this way, all the files you've actively downloading dissapears, the .met & .bak files are deleted. Sometimes other paused files dissapears too, but it seems to be randomly, or maybe caused by having 850+ files paused, that also makes aMule to have a strange behavior (lots of error 24 and error 2 messages).
If you want i could give you the backtrace (bt & bt full), but it seems to happen in every machine with 2.0.0rc8 i've tested, so you could easily obtain it. Also, because "bt" output sizes 6 MB and "bt full" output grows to 9 MB. Of plain text, of course.
For any question, just shout
