amule assert failure: *** buffer overflow detected ***: amule terminated

Bug #1279154 reported by Danilo Piazzalunga
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
amule (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Automatic crash report generated by apport.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: amule 2.3.1-11
ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AssertionMessage: *** buffer overflow detected ***: amule terminated
CurrentDesktop: Unity
Date: Wed Feb 12 03:15:08 2014
ExecutablePath: /usr/bin/amule
InstallationDate: Installed on 2013-12-27 (46 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: amule
ProcEnviron:
 LANGUAGE=it_IT
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: amule
StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f542b7148de "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:175
 __GI___fortify_fail (msg=<optimized out>, msg@entry=0x7f542b714875 "buffer overflow detected") at fortify_fail.c:37
 __GI___chk_fail () at chk_fail.c:28
 __fdelt_chk (d=<optimized out>) at fdelt_chk.c:25
 GSocket::Input_Timeout() () from /usr/lib/x86_64-linux-gnu/libwx_baseu_net-2.8.so.0
Title: amule assert failure: *** buffer overflow detected ***: amule terminated
UpgradeStatus: Upgraded to trusty on 2013-12-31 (43 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Danilo Piazzalunga (danilopiazza) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f542b7148de "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:175
 __GI___fortify_fail (msg=<optimized out>, msg@entry=0x7f542b714875 "buffer overflow detected") at fortify_fail.c:37
 __GI___chk_fail () at chk_fail.c:28
 __fdelt_chk (d=<optimized out>) at fdelt_chk.c:25
 GSocket::Input_Timeout() () from /tmp/apport_sandbox_b3yFVu/usr/lib/x86_64-linux-gnu/libwx_baseu_net-2.8.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in amule (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Seth Arnold (seth-arnold) wrote :

I believe this crash happened because the number of file descriptors open in the process was above 1024, the limit for the select() system call that is used in the underlying wxWidgets toolkit. I suggest using 'ulimit -n 1023' (or pick a smaller number) in whatever shell is used to start amule.

Ideally, amule would either manage its file descriptors more carefully or amule would switch to using the epoll API for socket readiness notification, either via a different wxWidgets API (if one is available) or managing its own sockets.

I suggest filing a bug with upstream amule developers.

Thanks for reporting this issue to Ubuntu.

information type: Private Security → Public
Changed in amule (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.