aMule Forum
English => aMule Help => Topic started by: dpcris85 on June 14, 2004, 07:30:31 PM
-
I don't think this is really a bug, so I post this here...
The problem is: while I am away, aMule is killed by "something".
The output of aMule doesn't report anything strange, only a "Killed".
This is my system log (/var/log/messages):
Jun 12 13:25:31 dpcris85-suse kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Jun 12 13:25:31 dpcris85-suse kernel: VM: killing process kdeinit
Jun 12 13:40:28 dpcris85-suse kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Jun 12 13:40:28 dpcris85-suse kernel: VM: killing process amule
Jun 12 13:43:36 dpcris85-suse kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Jun 12 13:43:36 dpcris85-suse kernel: VM: killing process kdeinit
Somebody knows what's happening? Thanks.
Info about my system:
Kernel: 2.4.21-215-athlon #1 Tue Apr 27 00:53:38 UTC 2004
Linux Version: SuSE Linux 9.0 Professional
-
looks like you run out of memory. When this happen kernel can kill process by itself
-
After a couple of days monitoring amule, I found that the running out of memory could be caused from a strange behaviour of amule: after I start it, the used memory grows slowly, even if the size of the amule thread reported in top doesn't change. When I close amule the memory isn't freed, and sometimes when I start amule the used memory increases suddenly of about 400 MB. Is this a (serious) bug of amule, or a (serious) bug of my kernel?
used memory before I start amule: 209176k
used memory ~3hrs after: 587700k
Info about my system:
Kernel: 2.4.21-226-athlon #1 Tue Jun 15 10:26:33 UTC 2004
Linux Version: SuSE Linux 9.0 Professional
-
I posted a backtrace (http://www.amule.org/amule/thread.php?threadid=2656&sid=) in the related section. Maybe it contains some usefuls info (I can't understand it, I'm a bad programmer - I only understood that it's something about CryptoPP)