aMule Forum
English => Backtraces => Topic started by: Lotta on April 15, 2016, 02:32:08 PM
-
Hi guys!
I'm reporting on an Assertion failed crash of aMule version 2.4.0~git20151120.0023527bc2-1 (from Debian Sid). No specific circumstances seem to trigger that crash, it just happens during normal operation without any user interaction, sometimes after less than one hour, sometimes after several days.
I'm experiencing these type of crashes already during several recent versions. Does the popping up of a GTK dialog (allowing to stop/continue and to save a backtrace) reflect an awareness of this problem? In any case, I've attached the gdb-backtrace as well as the one saved via the dialog.
Any more information I can provide?
-
I'm experiencing the same problem.
My current version is aMule SVN compiled with wxGTK2 v3.0.2 and Boost 1.58 running on Linux 4.4.0-21-generic x86_64 kernel on Ubuntu 16.04. Deb package version 2.4.0~git20151120.0023527bc2-1ubuntu1.
My backtrace can be found in the attached file.
-
I've reported on the origin of the problem here: http://forum.amule.org/index.php?topic=21322.0
-
Should be fixed now by revision 10922.