Print

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

[icoming]

Originally posted by thedude0001
walkin: There's a huge memleak in wx < 2.6.2 and I'm not sure if the workaround in amule was added before or after 2.0.3. Try upgrading wx & amule.

I think amule v2.1.3 has the memory leak too.
The wx I use is 2.7.0-1.

PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 1193 zhengda   25   0  610m 400m 9188 R 33.0 80.9  10:42.50 amule
 4194 root       6 -10 84436  18m 4096 S 27.0  3.7  30:46.38 XFree86
 4596 zhengda   16   0 72396 9224 6292 R 17.0  1.8   2:58.10 gnome-terminal

[Ezeltje]

Originally posted by icoming
I think amule v2.1.3 has the memory leak too.

Yep, I still encounter it every few days...

[icoming]

How to disable external conections?
Actually, I don't know whether it has been enabled, but I want a try.

[GonoszTopi]

Preferences > Remote Controls > Accept external connections

or

edit amule.conf, in the section [ExternalConnect] set AcceptExternalConnections=0

[icoming]

Then I haven't enabled it.
aMule must have some other functions which cause the memory leak.
Which latest version of aMule has not been report having the memory leak?

[Ezeltje]

Originally posted by icoming
aMule must have some other functions which cause the memory leak.
Which latest version of aMule has not been report having the memory leak?

v.2.0. It appears to have been introduced in v.2.1.1. I thought the addition of kad might be responsible for it, but I encounter the memleak even with kad turned off.

[icoming]

I think aMule 2.1.3 has another problem.
aMule runs for a while, and it uses the most resources in my computer.
  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
12368 zhengda   25   0  330m 247m  16m R 99.2 50.0  18:15.34 amule
 4587 root       5 -10 56368  34m 7428 S  0.3  7.0  25:22.79 XFree86

[regarding]

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=67
If 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=67
If 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).

[Ezeltje]

Originally posted by regarding
This bug only happens to me every few weeks

You are lucky then. The longest uptime I have seen since 2.1 is 12 days. Sometimes the memleak pops up after just 4 or 5 hours but on average it is about two days.

[Ezeltje]

Hi all,

I hate to nag, but is there any chance this bug will ever be fixed?

I just encountered it again this evening; in the course of about eight minutes, aMule went from around 100M/240M to 680M/1648M (real/virtual) memory use, thereby bringing my system to a halt and requiring a reboot. These are entries from a log updated every two minutes:

Code: [Select]

Fri Dec  8 00:42:02 CET 2006
aMule CVS Sun Dec  3 07:01:55 CET 2006 has been running for 4:21 h
xxxxxxx is connnnected to XXXXXXXXXXXXXX  [x.x.x.x:4242] with HighID | Kad: ok
Total Download: 1.32 Tb, Upload: 3.16 Tb
Session Download: 860.17 Mb, Upload: 424.04 Mb
Download: 53.6 kB/s, Upload: 27.1 kB/s
Sharing: 652 file(s), Clients on queue: 1705
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
xyz       7868  7.7  9.9 242352 103356 ?       RNl  Dec07  20:21 amule --even-if-lfroen-complains-this-will-stay

[...]

Fri Dec  8 00:50:05 CET 2006
aMule CVS Sun Dec  3 07:01:55 CET 2006 has been running for 4:22 h
xxxxxxx is connnnected to XXXXXXXXXXXXXX  [x.x.x.x:4242] with HighID | Kad: ok
Total Download: 1.32 Tb, Upload: 3.16 Tb
Session Download: 862.55 Mb, Upload: 425.29 Mb
Download: 58.3 kB/s, Upload: 31.7 kB/s
Sharing: 652 file(s), Clients on queue: 1701
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
xyz       7868  9.3 66.4 1648336 686984 ?      DNl  Dec07  25:04 amule --even-if-lfroen-complains-this-will-stayAs I mentioned before in this thread, I first encountered this memory leak in January with v2.1.1. I really hope this gets fixed eventually.

Code: [Select]

$ rpm -qa | grep wx
wxGTK-gl-2.6.3-2.6.3.2.3.fc6
wxGTK-devel-2.6.3-2.6.3.2.3.fc6
wxGTK-2.6.3-2.6.3.2.3.fc6

[Ezeltje]

...and again tonight: after an uptime of 1 hour, 43 minutes  X( X( X(

Code: [Select]

aMule CVS Sun Dec  3 07:01:55 CET 2006 has been running for 1:43 h
xxxxxxx is connnnected to XXXXXXXXXXXXXX  [x.x.x.x:4242] with HighID | Kad: ok
Total Download: 1.33 Tb, Upload: 3.16 Tb
Session Download: 326.13 Mb, Upload: 172.89 Mb
Download: 50.7 kB/s, Upload: 39.7 kB/s
Sharing: 657 file(s), Clients on queue: 2332
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
xyz       3458 13.1 82.1 1713464 849312 ?      DNl  00:01  14:45 amule --even-if-lfroen-complains-this-will-stay

[phoenix]

Ezeltje,

aMule runs in my computer for days without noticeable increase in memory usage, and believe me, I do stress aMule. I stress it to the point that I have reached a limit of open files in my system, when aMule starts to download like 800 files, it starts to fail. My next task will be to test a patch from a user that claims to only open the files when they are needed, thus increasing that limit a lot. My memory consumption is always around 10-13%. I have 512 mega of ram. I share 1580 files.

Code: [Select]

aMule CVS rev. 6988 has been running for 4:18 h
xxxxxxxxxx is connnnected to xxxxxxxxxxxxxxxx [xxx.xxx.xxx.xxx:xxxx] with HighID | Kad: ok
Total Download: 948.26 Gb, Upload: 345.63 Gb
Session Download: 491.68 Mb, Upload: 328.31 Mb
Download: 58.0 kB/s, Upload: 23.7 kB/s
Sharing: 1580 file(s), Clients on queue: 5000
$ ps u -C amule
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
xxxxxx   31592 21.4 10.0 263472 103576 pts/3   Dl+  Dec08  55:30 /home/xxxxxx/amule --even-if-lfroen-complains-this-will-
Maybe your leak is somewhere else, maybe in wxGTK or gtk itself. I have heard that there could be a problem between two certain versions of wxGTK and gtk.

[Ezeltje]

Originally posted by phoenix
aMule runs in my computer for days without noticeable increase in memory usage, and believe me, I do stress aMule. I stress it to the point that I have reached a limit of open files in my system, when aMule starts to download like 800 files, it starts to fail.

Wow, reminds me of DOS days (<1990). Remember the default FILES=20 in config.sys?  

I had also thought I was stressing aMule too much, sharing 1600 files (~600Gb), so I experimented for a few days with just sharing my current downloads, but it didn't make much difference in stability.

Maybe your leak is somewhere else, maybe in wxGTK or gtk itself. I have heard that there could be a problem between two certain versions of wxGTK and gtk.

I am going to use amuled for the next week or so. If your hypothesis is correct, then I shouldn't see the leak. wx/gtk is only used for GUI stuff, right?

Later, I will also try running amule under Ubuntu to see if that makes any difference.

Thanks for the reply.

[phoenix]

Originally posted by Ezeltje
I am going to use amuled for the next week or so. If your hypothesis is correct, then I shouldn't see the leak. wx/gtk is only used for GUI stuff, right?

Later, I will also try running amule under Ubuntu to see if that makes any difference.

Thanks for the reply.

Excelent idea! Please report your findings.

[Ezeltje]

I now have an uptime with amuled of 21 days, so I think I can safely say the mem leak is not in the core:

Code: [Select]

$ cas
aMule CVS Sat Dec 16 07:01:50 CET 2006 has been running for 21 D 14 h
xxxxxxxxxx is connnnected to xxxxxxxxxxxxxxxx [xxx.xxx.xxx.xxx:xxxx] with HighID | Kad: off
Total Download: 1.40 Tb, Upload: 3.31 Tb
Session Download: 11.52 Gb, Upload: 71.57 Gb
Download: 2.8 kB/s, Upload: 45.0 kB/s
Sharing: 239 file(s), Clients on queue: 763(BTW, I don't know why cas reports "Kad: off"; kad searches with amulecmd work fine.)

Virtual memory use has crept up to 637 MB, which seems like a lot:

Code: [Select]

$ ps u -C amuled
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
xyz       3196  1.4  6.6 637488 68712 ?        Ssl   2006 465:38 amuled -fbut resident memory is only 68 MB and at least it hasn't gone haywire.

At this point, I am considering running aMule monolithic under Ubuntu for awhile. Rather than copy ~/.amule to my laptop (../incomplete = ~15 Gb) I am thinking of just mounting it as an NFS share. Is this a Bad Idea???

Another option might be to download and compile v2.8 of wxGTK on my FC6 box to see if it fixes the memleak under Fedora, but only if it won't trash vlc, my main media player. Thoughts anyone?