After passing the Cerberus at the registration in the 8th attempt, please allow me to offer my extreme solution: I use aMule for some years already, and this bug or a bug like this was around for something like years too. I really can't live without aMule, but when it crashes every two hours it's of little use. So I tried to see what was the problem with valgrind, but it reported something of an order of a million errors, so I really couldn't find my way there. Finally I wrote a simple script that enabled me to use aMule again:
#!/bin/bash
MAXPERC=20
while true ;
do
PERC=$(ps -C amule -o %mem=)
echo amule is using $PERC% of the physical memory. We kill it at $MAXPERC%.
#if [[ $PERC > 20 ]]
if [[ $(echo "r=0;if($PERC>$MAXPERC)r=1;r" | bc) == 1 ]]
then
killall -KILL amule
sleep 10
echo amule --display :0 | at now
fi ;
sleep 5
done
So I check if aMule takes more than 20% of the total physical memory once in five seconds, and if it does, I kill it, wait 10 seconds, and then start it again.
I know, it's terrible... But I can start many downloads, use the bandwidth fully, go to sleep, and the next day aMule is still downloading.