On Mon, Aug 10, 2015 at 4:25 AM, Dmitry Smirnov <only...@debian.org> wrote: > On Debian "testing" aMule leaks memory somewhere -- today I had to terminate > it when I've noticed that "amule" process grew to occupy ~20 GiB or "RES" > memory. Only Kademlia network is active (ED2K is disabled)...
Can you set a lower memory limit for amule, install amule-dbg, run amule in gdb and generate a backtrace as described at : http://wiki.amule.org/wiki/Backtraces#Create_a_backtrace - this way I can forward this bug upstream. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org