Your message dated Sat, 16 Feb 2019 20:11:42 -0500 with message-id <cab4xwxzpf8bfgmgevff_h5wdbqwsxxp5qo2gm2y6y_zazac...@mail.gmail.com> and subject line amule: closing bugs without followups has caused the Debian Bug report #795058, regarding amule: memory leak to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 795058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795058 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: amule Version: 2.3.1+git1a369e47-3 Severity: normal 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)... --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: stretch/sid 500 testing-updates httpredir.debian.org 500 testing security.debian.org 500 testing httpredir.debian.org 333 unstable httpredir.debian.org 1 experimental httpredir.debian.org --- Package information. --- Depends (Version) | Installed =====================================-+-=================== amule-common (= 2.3.1-11) | 2.3.1+git1a369e47-3 libc6 (>= 2.14) | libcrypto++9 | libgcc1 (>= 1:4.1.1) | libgeoip1 | libstdc++6 (>= 4.6) | libupnp6 (>= 1:1.6.13) | libwxbase2.8-0 (>= 2.8.12.1+dfsg) | libwxgtk2.8-0 (>= 2.8.12.1+dfsg) | zlib1g (>= 1:1.1.4) | Recommends (Version) | Installed ==========================-+-=========== amule-utils | 2.3.1+git1a369e47-3 unzip | 6.0-17 -- Regards, Dmitry Smirnov
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---This bug hasnt received any followup from the reporter, hence closing. Please reopen if you can provide additional information.
--- End Message ---
