Your message dated Sat, 03 Oct 2026 16:14:05 -0400 with message-id <E1xD67R-0000000CCsr-0qqx@zion> and subject line Re: Bug#772592: amule: occasional segmentation fault has caused the Debian Bug report #772592, regarding amule: occasional segmentation fault 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.) -- 772592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772592 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: amule Version: 2.3.1+git1a369e47-3 Severity: normal I used all my quota this month and my ISP throttled connection to 512/512. That's when amule begin to crash -- it works for less than an hour until "Segmentation fault". I have only KAD enabled and I have a feeling that it may be related to number of simultaneous connections (although lowering max simultaneous connections from 900 to 90 did not help). No errors are logged to console and I tried to run amule under GDB for a while but under GDB it is slow and problem do not manifest. Without GDB it crashes in 30...60 min. I think on fast connection I've seen few occasional segfaults in the past but it was not unusual for amule to last for days and even weeks while now I have an hour at most. This is on up-to-date Jessie. I'm out of ideas how to troubleshoot further... --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 -- All the best, Dmitry Smirnov GPG key : 4096R/53968D1B --- Theology is but the ignorance of natural causes reduced to a system. -- Baron Paul Henri T. d'Holbach
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---Hi, The backtrace shows the crash in wxSocket and GLib, called from aMule's upload throttler thread. aMule's network code now uses only Boost.Asio and no longer goes through wxSocket for client connections, so this code path doesn't exist anymore. Closing; please open a new bug with a backtrace if aMule still crashes for you. Regards, Sandro
--- End Message ---
