aMule : makes computer hang after a few hours ??

[Vincent Trouilliez]

Hi,

I am having a problem with aMule. I installed it (on Dapper) earlier
today, and a after only a few hours running, it causes the computer to
slow down and becomes sluggish/unresponsive. I bet it would just hang if
I left it like this for a few more hours :-/

I looked in Gnome system monitor, and amule created about 45 (!)
"zombie" processes !!! But the main amule process uses very little CPU
time, and although I am downloading 300 files at the same time, I still
have plenty of RAM left and nothing on the swap, so I couldn't figure
out why it would slow down the whole machine... until I looked at root
processes : Xorg uses 75% of the CPU !! :-O

And all that after only 4 hours or so of using aMule. Is this "normal",
is aMule still beta software ? And how comes Xorg comes into play, I
thought it was only there to deal with mouse/keyboard/screen/network
eventually ??
Is this a known problem, is there a known solution to recover the system
responsiveness without having to kill/quit aMule (as it takes time to
enter queues) ?
The way I thought P2P worked, was to select bags of files and let the
machine running 24/7 to retrieve chunks of files at snail pace and
slowly put everything together over time ? So surely it's not designed
to put the machine all over the place in only a few hours ?!?

Thanks for sharing your experiences/suggestions...


Regards,


--
Vince, would like an efficient P2P program...