After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 671493 - empathy crashed with SIGSEGV in malloc_consolidate()
empathy crashed with SIGSEGV in malloc_consolidate()
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: .General
3.3.x
Other Linux
: Normal critical
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2012-03-06 20:24 UTC by Bilal Shahid
Modified: 2013-10-14 06:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bilal Shahid 2012-03-06 20:24:31 UTC 
Originally reported at:
  https://bugs.launchpad.net/bugs/945391

I was doing nothing. It was been running in the background, and suddenly crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: empathy 3.3.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.93-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sat Mar  3 01:38:42 2012
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120227)
ProcCmdline: empathy
SegvAnalysis:
 Segfault happened at: 0xb4f46cd8:	cmp    0xc(%eax),%edi
 PC (0xb4f46cd8) ok
 source "0xc(%eax)" (0x000016a5) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 malloc () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_malloc () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: empathy crashed with SIGSEGV in malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Comment 1 Bilal Shahid 2012-03-06 20:24:57 UTC 
>>stacktrace
https://launchpadlibrarian.net/95077911/Stacktrace.txt
Comment 2 Akhil Laddha 2012-03-07 05:11:30 UTC 
mostly gtk related trace
Comment 3 Guillaume Desmottes 2012-03-07 09:19:59 UTC 
Indeed, re-assigning to GTk+ then.
Comment 4 Christian Persch 2012-03-07 13:39:34 UTC 
This looks like random memory corruption, not a gtk bug. Try valgrinding.
Comment 5 Timothy Arceri 2013-10-14 06:36:34 UTC 
Upstream bug has been closed. Marking as obsolete as valgrind information was never provided.