I've noticed my system becoming really sluggish and 100% out of memory as shown by GNOME
System Monitor. Never knew what program was doing it til today. I was able to ssh in from another
machine and run "top", showing 1400+ Mbyte amule process. When I created a new swapfile and
did "swapon" to it, within seconds amule had eaten another 64 megs. I added two more 128 meg
swapfiles and those got eaten too. But I was able to kill -ILL the amule process, hoping to get
a core file or something that would allow this to be debugged.
Unfortunately, amule contains some silly signal catcher which prevents it from dumping core --
instead I got this output:
$ kill -ILL %3
$
--------------------------------------------------------------------------------
A fatal error has occurred and aMule has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
http://forum.amule.org/board.php?boardid=67If possible, please try to generate a real backtrace of this crash:
http://www.amule.org/wiki/index.php/Backtraces----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMule 2.1.3 using wxGTK2 v2.6.3 (Unicoded)
Running on: Linux 2.6.11-1-k7-smp i686
[then a lot of BEEPs, as if control-G was being output many times...]
$ jobs
[3]+ Running amule & (wd: ~)
$ kill -ILL %3
$
--------------------------------------------------------------------------------
A fatal error has occurred and aMule has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
http://forum.amule.org/board.php?boardid=67If possible, please try to generate a real backtrace of this crash:
http://www.amule.org/wiki/index.php/Backtraces----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMule 2.1.3 using wxGTK2 v2.6.3 (Unicoded)
Running on: Linux 2.6.11-1-k7-smp i686
[2] ?? in amule [0x8083d46]
[3] wxFatalSignalHandler in /usr/lib/libwx_baseu-2.6.so.0[0xb75b66c8]
[4] ?? in [0xffffe420]
[5] wxMilliSleep(unsigned long) in /usr/lib/libwx_baseu-2.6.so.0[0xb75b4705]
[6] wxThread::Sleep(unsigned long) in /usr/lib/libwx_baseu-2.6.so.0[0xb75ac84f]
[7] ?? in amule [0x8117df4]
[8] wxThreadInternal::PthreadStart(wxThread*) in /usr/lib/libwx_baseu-2.6.so.0[0xb75ac1c6]
[9] wxPthreadStart in /usr/lib/libwx_baseu-2.6.so.0[0xb75ac03f]
[10] ?? in /lib/tls/libpthread.so.0 [0xb7fcab63]
[11] __clone in /lib/tls/libc.so.6[0xb734d18a]
--------------------------------------------------------------------------------
[3]+ Aborted amule (wd: ~)
Note that I had to kill it twice to get any meaningful output.
This bug only happens to me every few weeks, it seems. I use both kad and ed2k.
I had external connections enabled, but wasn't using it (it was there for running amule-daemon,
but I discovered amule-daemon didn't support double clicking on a file to see what peers have
it, which I use a lot, so I stopped using it).