Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Ezeltje]

I downloaded v2.1.1 and compiled it this afternoon. After running ~3 1/2 hours, amule was using 1148m virtual, 784m shared memory, according to top. If there is any way I can help track this problem down, please let me know.

[Kry]

amule --version

[Ezeltje]

$ ./amule --version
aMule 2.1.1 using wxGTK2 v2.6.2 (Unicoded) (OS: Linux)

[Kry]

Do you use EC?

[Ezeltje]

You mean External Connections? Yes, for quite some time.

[Ezeltje]

Update: I've had 2.1.1 running now for ~7 hours, and memory usage appears to have stabilized at 106m RES and 147m VIRT. Apparently, the mem leak only happens under very specific circumstances...

[Kry]

There is a potentially huge memleak on EC I fixed yesterday, will be ok on 2.1.2 (which would be.... soon)

[Ezeltje]

Originally posted by Kry
There is a potentially huge memleak on EC I fixed yesterday, will be ok on 2.1.2 (which would be.... soon)

Has this made it into the CVS version? I am running the 1 April tarball and just now the memory leak once again completely choked my system; it became unresponsive and I had to hit the reset button. Although I had EC enabled, I wasn't using it, but for the time being I have disabled it.

I really like amule -- but not when it nukes my system. ;(

[Kry]

aMule can't nuke your system. Which wx are you using?

[Ezeltje]

Never mind. it appears that it was a CUPS program called footmatic-rip that was choking my system. Problem was that I couldn't open top in time to find out what the culprit was... Sorry for the false alarm.

[Kry]

Told ya, told ya....

[Ezeltje]

My system spontaneously started thrashing again this morning and this time it did in fact turn out to be caused by amule. Although the system became unresponsive, I was finally able to shutdown X with ctrl-alt-backspace and log into a failsafe terminal. Here is the output from top which I saved to disk:

Code: [Select]

$ cat toplog.txt

top - 12:19:25 up 1 day, 11:41,  3 users,  load average: 1.69, 9.37, 12.31
Tasks:  95 total,   1 running,  94 sleeping,   0 stopped,   0 zombie
Cpu(s): 20.6% us,  1.9% sy,  0.0% ni,  0.0% id, 77.5% wa,  0.0% hi,  0.0% si
Mem:   1035176k total,  1020624k used,    14552k free,      620k buffers
Swap:  1020116k total,   534784k used,   485332k free,    10812k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 3049 jrb       18   0 1339m 899m 2492 D 21.1 89.0 262:51.90 amule
  157 root      15   0     0    0    0 S  0.3  0.0   0:37.54 kswapd0
 2347 root      15   0     0    0    0 S  0.3  0.0   0:10.13 nfsd
    1 root      16   0  1992  104   80 S  0.0  0.0   0:01.22 init
    2 root      34  19     0    0    0 S  0.0  0.0   0:00.48 ksoftirqd/0
    3 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 watchdog/0
    4 root      10  -5     0    0    0 S  0.0  0.0   0:00.32 events/0
    5 root      10  -5     0    0    0 S  0.0  0.0   0:00.00 khelper
    6 root      10  -5     0    0    0 S  0.0  0.0   0:00.00 kthread
    8 root      10  -5     0    0    0 S  0.0  0.0   0:00.62 kblockd/0
    9 root      20  -5     0    0    0 S  0.0  0.0   0:00.00 kacpid
  100 root      10  -5     0    0    0 S  0.0  0.0   0:00.00 khubd
  158 root      18  -5     0    0    0 S  0.0  0.0   0:00.00 aio/0
  245 root      10  -5     0    0    0 S  0.0  0.0   0:00.02 kseriod
  320 root      11  -5     0    0    0 S  0.0  0.0   0:00.00 kpsmoused
  336 root      10  -5     0    0    0 S  0.0  0.0   0:00.02 ata/0
  340 root      11  -5     0    0    0 S  0.0  0.0   0:00.00 scsi_eh_0
As you can see, amule was still running and using a catastrophic amount of memory, nearly 900M on a 1 GB machine. For some reason it had not responded to the Gnome logout and I could only terminate it with killall -9.

FWIW: amule had been running about 36 hours. Yes, I am sharing a lot of files.

At this point, I don't think it has anything to do with ext connections; I had that function disabled and amuleweb was not running. This is the 1 April CVS with wxGTK-2.6.2-5.fc5.

Let me know if I can supply any additional information...

[Ezeltje]

This time amule ran fine for about three days, then suddenly started gobbling up memory. I captured the top output in a terminal window on my laptop:

Code: [Select]

$ top

top - 20:05:51 up 4 days, 19:28,  5 users,  load average: 14.24, 7.73, 4.17
Tasks: 168 total,   1 running, 166 sleeping,   0 stopped,   1 zombie
Cpu(s):  1.6% us, 10.9% sy,  0.0% ni,  0.0% id, 87.4% wa,  0.0% hi,  0.0% si
Mem:   1035176k total,  1022996k used,    12180k free,      548k buffers
Swap:  1020116k total,  1020116k used,        0k free,    21536k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
22470 jrb       17   0 1218m 682m 2436 D  1.0 67.5 611:06.59 amule
32682 jrb       16   0  215m  63m 3412 D  0.5  6.3   0:28.74 firefox-bin
23291 jrb       16   0  299m  49m 1992 D  0.5  4.9  10:23.91 thunderbird-bin
22155 root      16   0  160m  30m 1788 D  1.3  3.0 905:14.19 Xorg
[...]
Although the desktop box became unresponsive, I fortunately got to my laptop in time to kill amule via this terminal window.

I am the only one having this problem???

[Kry]

Seems so. weird.

[Ezeltje]

Could there possibly be something in the 2.1 kad code? As I mentioned earlier in this thread, I never had this problem with 2.03, which I ran for many weeks, sometimes months at a time.