[Expired for amule (Ubuntu) because there has been no activity for 60
days.]
** Changed in: amule (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/162341
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
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
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
Yes, now I use Karmic, but this bug is quite old. It sucks to reinit
amule two or three times each week.
--
amule leaks 0.2 MiB memory per hour
https://bugs.launchpad.net/bugs/162341
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
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.
** Changed in: amule (Ubuntu)
Status: Incomplete = Confirmed
--
amule leaks 0.2 MiB memory per hour
Any changes in amule package of jaunty?
** Changed in: amule (Ubuntu)
Status: Confirmed = Incomplete
--
amule leaks 0.2 MiB memory per hour
https://bugs.launchpad.net/bugs/162341
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
** Changed in: amule (Ubuntu)
Status: New = Confirmed
--
amule leaks 0.2 MiB memory per hour
https://bugs.launchpad.net/bugs/162341
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: amule (Ubuntu)
Status: Incomplete = New
--
amule leaks 0.2 MiB memory per hour
https://bugs.launchpad.net/bugs/162341
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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.
** Attachment added: valgrind.amule.log.gz
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
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.
** Changed in: amule (Ubuntu)
Status: New =
Since 2.1.3 is totally unmaintained upstream, could you please check
whether this still happens with aMule 2.2.0 in Hardy?
Thanks.
** Changed in: amule (Ubuntu)
Importance: Undecided = Low
Status: New = Incomplete
--
amule leaks 0.2 MiB memory per hour
14 matches
Mail list logo
