This is my first post, so hello everyone.
I have been using aMule for quite some time, but some time ago it started mysteriously crashing. The errors I got spit out to the console were exactly the same as here:
http://forum.amule.org/index.php?topic=14957.0I noticed that always happened when I started aMule, and it tried to connet to one of the servers (not one of the top servers according to the number of files) - the log in Amule tab said "connection lost" and stuff like that, and crashed afterwards. So what I did was:
1. sorted the servers by the number of files (click on the "Files" column header, so that the one with the biggest number is on top)
2. picked 5-6 top servers, and deleted all the others (EDonakyServers, Razorbacks)
3. uncheck the options to update server lists on connection to server and on client connect (Preferences->Server)
4. restart
Since yesterday, my amule has been running and downloading stuff, hasn't had a single crash.
Probably you don't have to delete the servers, just pick the best ones and mark them high priority or maybe static (and check the connect on startup only to statici server option), so that the faulty servers don't crash your client.
I'm not sure which server was the culprit, I don't remember the name), I am not sure if any of this works for you guys (and girls) here, I completely don't know if what I'm writing here makes any sense in the technical point of view (what I remember is that when the connection was lost, some thread scheduler msgs were output, and then it would die - maybe some part of this code are the causes in general for amd64??). All I know is that _my_ aMule would crash every single time, and has been stable ever since I did what I did. 24 hrs may not be the greatest test to prove it works, but is is more than a few minutes as before that.
It worked for me, so I wanted to share that, maybe it will work for others?
Cheers.
