Print

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

[Arichy]

Originally posted by Kry
Try with wxCVS

Using newer wx-gtk seems to be the solution.

I have compiled wx-cvs-gtk from 2005-09-09 and aMule-CVS from 2005-09-06.

aMule is now running for five days.

In the first some ten hours the memory and swap usage increased, but then it got stable at 82 of 92 MB RAM and 47 of 94 MB swap.

[Arichy]

I have to revoke my posting from yesterday.

As I see, aMule crashed just 30 Minutes after my posting yesterday, at 23:03.

There is just one error line in /var/log/messages:

Code: [Select]

Sep 18 23:03:20 localhost kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
After automatic restart at 23:04 (script), aMule is running faster again.

Memory usage is now (09;15) 63 MB RAM (of 92 MB) and 45 MB swap (of 94 MB).

[Arichy]

aMule crashed again after 17h running.

No messages on that in /var/log/messages or /var/log/syslog

[phoenix]

This is probably a leak in either aMule or wx. As you use few RAM, the leak is more serious in your system.

[zekkerj]

Hi all, same problem here.

aMule starts smoothly, after a few days it eats all of my available memory. ;(

Output of "amule --version":

aMule 2.0.3 using wxGTK2 v2.5.4 (OS: Linux)

Celeron 1GHz,
RAM 256MiB
Swap 265MiB

Output of "uname -a":

Linux ithilien.casa 2.6.11-72032U10_17clcustom #1 Tue May 3 21:29:30 BRT 2005 i686 unknown unknown GNU/Linux

Is there any debugging switch I can use to build a trace of memory allocation?

[Kry]

Use wx 2.6.2

[zekkerj]

Geeeeez, another recompile...  

[lupz]

if you can't find the memory leak, who has a powerful machine to keep up an amule istance two days using valgrind ?
Valgrind

Code: [Select]

valgrind --leak-check=full /path/to/amule
valgrind --tool=addrcheck --leak-check=full /path/to/amule (it's about twice faster but less accurate)it will find a lot of leaks

the machine on which it runs, should have a powerful processor and *a lot* of RAM

it runs about 10 times slower than the real thing.. but on exit it reports all the memory that the software has wasted with the backtrace of the call that lost it!

[Kry]

It's already fied on wx2.6.2, read some posts above. It was not aMule.

[lupz]

Originally posted by Kry
It's already fied on wx2.6.2, read some posts above. It was not aMule.

I suspected something like that because on my run on valgrind a lot of wasted space resulted from lost references of wxStringBase objects.

I've compiled over wx 2.6.2 but it crashes on start some nigthly ago.. i'll try again with tomorrow build

[Arichy]

Because wx-gtk CVS from 2005-09-09 did not help, I fell back on aMule 2.0.3 from the dude.gemil.de Debian packages.

With that, there are nor memory problems, only 50% usage, stable.

[Arichy]

Originally posted by Kry
It's already fied on wx2.6.2, read some posts above. It was not aMule.

Still problems:

With aMule-CVS-2005-10-22 source code from amule homepage compiled with libwxgtk 2.6.2-1 from dude.gemil.de debian package repository the memory gets eaten up (from 47 to 77 MB of 92 MB RAM in 48h, then slower decreasing free memory until crash after some days).

With aMule-2.0.3 source code from amule homepage compiled with the same libwxgtk 2.6.2-1 from dude.gemil.de debian package repository the memory usage is stable low at 32 MB of 92 MB RAM.

[Kry]

It's CVS. Might have leaks.

[Arichy]

Originally posted by Kry
It's CVS. Might have leaks.

Unfortunately, it seems to have leaks indeed:

aMule-CVS from 2005-11-30 (self compiled) with wxgtk 2.6.2 package from dude.gemil.de on Debian Sarge (Kernel 2.4.27):

After 36h running:
80 MB of 92 MB RAM used
73 MB of 94 MB Swap used

Computer awfully slow (no much time and it will crash I think)

Greets, Arichy

PS Do not have a powerful computer for using valgrind (it is an Pentium III).
If there is another possibility for me to help You, please tell me.

[Xaignar]

Can you run "amule --version" and paste the output?