amule crashed with SIGSEGV in g_source_remove()

[LAZA]

aMule crashed at night, BOINC running.
Maybe the bug report will bring some light into it....

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: amule 2.3.1-11
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Fri Oct 10 01:42:51 2014
ExecutablePath: /usr/bin/amule
InstallationDate: Installed on 2014-03-16 (207 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140225)
ProcCmdline: amule
SegvAnalysis:
 Segfault happened at: 0x7f98a15ec36b <malloc_consolidate+299>: mov 0x10(%rbx),%rax
 PC (0x7f98a15ec36b) ok
 source "0x10(%rbx)" (0xcd70fedb93875aff) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: amule
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_source_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 GSocketGUIFunctionsTableConcrete::Install_Callback(GSocket*, GSocketEvent) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
 GSocket::Write(char const*, int) () from /usr/lib/x86_64-linux-gnu/libwx_baseu_net-2.8.so.0
Title: amule crashed with SIGSEGV in g_source_remove()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare sudo tape video

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1156582, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.