amule leaks 0.2 MiB memory per hour

[Harald Rudell]

Binary package hint: amule

in Ubuntu gutsy 7.10, amule from the package amule 2.1.3-3ubuntu1 leaks memory about 0.2 MiB per hour, limiting the uptime to something like 30 days

Since it crashed my metal-hardware, I ran it in vmware with System monitor open, process tab, sorted by Memory. Others have reported this bug for feisty, http://forum.amule.org/index.php?PHPSESSID=3249abd8ca407acc8c77f06999cf8fb8&topic=12522.msg66963#msg66963 the programmer swears a clean recompile will solve the problem.

any comment from the maintainer?

[Emilio Pozuelo Monfort (pochu)]

Since 2.1.3 is totally unmaintained upstream, could you please check whether this still happens with aMule 2.2.0 in Hardy?

Thanks.

[Denis Rut'kov (dendron2000)]

I tried several versions of amule, every version has this bug. Currently I have aMule SVN using wxGTK2 v2.8.4 (Snapshot: Wed Jan 16 07:01:56 CET 2008).
The huge memory leak makes amule unusable, as it would crash within a day. My OS is Xubuntu 7.10.
I heard it has something to do with wxWidgets+gtk2.

[Emilio Pozuelo Monfort (pochu)]

Well, 0.2 MB per hour would be less than 5 MB a day. I won't say that will make aMule crash in a day. But it's still a leak and should be fixed, so could you get a valgrind log to see where is the leak?
https://wiki.ubuntu.com/Valgrind

Thanks.

[Evgeny Kuznetsov (nekr0z)]

Here I have a valgrind log running the current aMule from repositories on Hardy. I stopped the program when valgrind said there were too many errors and further errors shall not be logged. It took less than 20 hours of runtime to reach it.

[Oibaf (oibaf)]

2.2.2 in intrepid is till leaking:

==8433== ERROR SUMMARY: 43559 errors from 242 contexts (suppressed: 272 from 2)
==8433== searching for pointers to 301,307 not-freed blocks.
==8433== checked 23,303,976 bytes.
==8433==
==8433== LEAK SUMMARY:
==8433== definitely lost: 81,701 bytes in 2,685 blocks.
==8433== possibly lost: 1,184,632 bytes in 6,210 blocks.
==8433== still reachable: 12,597,032 bytes in 292,412 blocks.
==8433== suppressed: 0 bytes in 0 blocks.
==8433== Rerun with --leak-check=full to see details of leaked memory.

[Festor (festor-deactivatedaccount)]

Any changes in amule package of jaunty?

[Oibaf (oibaf)]

Both 2.2.3 (from official ubuntu packages) and 2.2.4 (still not in Ubuntu) are leaking, as well as showing a lot of errors when running under valgrind.

[Silvano (silvano-jorge)]

Yes, now I use Karmic, but this bug is quite old. It sucks to reinit amule two or three times each week.

[shankao (shankao)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at http://wiki.amule.org/index.php/Bug_report. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[shankao (shankao)]

Is there any news about this bug? Has someone affected by this bug sent the report upstream? Could you tell us the bug number, so we can add a bugwatch that will inform us about its status.? Thanks in advance.

[shankao (shankao)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Precise Pangolin. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

[Launchpad Janitor (janitor)]

[Expired for amule (Ubuntu) because there has been no activity for 60 days.]