Hello there,
My aMule (monolithic) just doesn't respond anymore. It seems to be working (hashing files or something), but the GUI doesn't respond to anything at all. I've been using aMule since version 2.0.0, and 2.1.3 for several months now, and it has never acted this way before, even when hashing quite a lot of large files!
It's just that a few hours ago, the GUI froze and didn't respond anymore, and CPU usage fluctuated from 60% to 99%. After half an hour or so, I killed amule and restarted it. The GUI appeared, but it froze even before connecting to a server. It seems to be doing something, according to "top" (still 60% to 99% CPU load), but it is certainly not transferring any files.
Now WTF is my amule doing there? And how can I make it work again?
I tried rebooting the system, using a 2.4.x kernel instead of 2.6.8, I even tried moving the .aMule/Temp/ directory somewhere else, deleting the entire .aMule directory, starting it again and going through the entire setup process once again, terminating amule, moving the Temp directory back and starting it again. That seemed to work for a while, it had to rehash all the shared files again, but the transfers started, and the GUI worked. But then, after an hour or so, it went back to the state of not responding anymore, not transferring anything, while still using lots of CPU power...