aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: aMule killed  (Read 2681 times)

dpcris85

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 11
  • Well... dark brown hair & eyes, 1.74 m, < 80 kg. I love Math, Linux, Nutella (www.nutella.it), trains, Harry Potter's books, driving my friends crazy talking them about quantistic mechanic or hyperspaces.
    • http://dpcris85.homelinux.net
aMule killed
« 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
Logged

lfroen

  • Guest
Re: aMule killed
« Reply #1 on: June 15, 2004, 11:48:32 AM »
looks like you run out of memory. When this happen kernel can kill process by itself
Logged

dpcris85

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 11
  • Well... dark brown hair & eyes, 1.74 m, < 80 kg. I love Math, Linux, Nutella (www.nutella.it), trains, Harry Potter's books, driving my friends crazy talking them about quantistic mechanic or hyperspaces.
    • http://dpcris85.homelinux.net
Re: aMule killed
« Reply #2 on: June 17, 2004, 12:02:44 PM »
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
« Last Edit: June 17, 2004, 06:06:18 PM by dpcris85 »
Logged

dpcris85

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 11
  • Well... dark brown hair & eyes, 1.74 m, < 80 kg. I love Math, Linux, Nutella (www.nutella.it), trains, Harry Potter's books, driving my friends crazy talking them about quantistic mechanic or hyperspaces.
    • http://dpcris85.homelinux.net
Re: aMule killed
« Reply #3 on: June 23, 2004, 10:57:17 PM »
I posted a backtrace 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)
Logged