GNOME Bugzilla – Bug 671740
empathy-chat crashed with SIGSEGV in malloc_consolidate()
Last modified: 2012-04-08 09:56:18 UTC
Originally reported at: https://bugs.launchpad.net/bugs/949393 closing a chat window ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: empathy 3.3.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Wed Mar 7 22:06:33 2012 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcCmdline: /usr/lib/empathy/empathy-chat SegvAnalysis: Segfault happened at: 0x7fe1c0ee5b38: mov 0x10(%rbx),%rdx PC (0x7fe1c0ee5b38) ok source "0x10(%rbx)" (0xffff801e3ec1df30) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: empathy StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 g_object_run_dispose () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: empathy-chat crashed with SIGSEGV in g_object_run_dispose() UpgradeStatus: Upgraded to precise on 2012-02-18 (18 days ago) UserGroups: adm admin cdrom dialout dip fax floppy fuse games lpadmin plugdev sambashare tape video
>> xsession error : https://launchpadlibrarian.net/95801479/XsessionErrors.txt >> stacktace https://launchpadlibrarian.net/95918719/Stacktrace.txt
Bilal: I've asked you in several of your past bug reports that you set severity to "critical" when you forward crashers, and also that you paste the stacktrace in GNOME Bugzilla instead of just pasting a link. What is so hard about it that you cannot follow this request?
sir i am really very soryy all about these bugs,, i assure you that i will never do it again.
Could you please paste the content of the stacktraces for those bug reports inline (=as a comment instead of adding an attachment)? Thanks!
Created attachment 209401 [details] >> stacktrace
In comment 4 I asked to ****NOT**** attach it as an attachment. Sigh.
+ Trace 229846
Looks like a memory corruption. Any chance to have a valgrind log?
no more crashes