empathy assert failure: *** glibc detected *** empathy: double free or corruption (fasttop): 0x0000000001acb690 ***

[Cristian Aravena Romero]

Binary package hint: empathy

Work with empathy and open apport

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: empathy 2.32.1-0ubuntu1
Uname: Linux 2.6.37-020637rc5-generic x86_64
Architecture: amd64
AssertionMessage: *** glibc detected *** empathy: double free or corruption (fasttop): 0x0000000001acb690 ***
Date: Tue Dec 7 21:37:59 2010
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: empathy
ProcEnviron:
 LANG=es_ES.utf8
 SHELL=/bin/bash
Signal: 6
SourcePackage: empathy
StacktraceTop:
 raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __libc_message (do_abort=<value optimized out>, fmt=<value optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=3, str=0x7f08307d7030 "double free or corruption (fasttop)", ptr=<value optimized out>) at malloc.c:6283
 __libc_free (mem=<value optimized out>) at malloc.c:3738
Title: empathy assert failure: *** glibc detected *** empathy: double free or corruption (fasttop): 0x0000000001acb690 ***
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1392): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1376): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

[Guillaume Desmottes (cassidy)]

Looking at the trace I don't see any reason why this code would fail so I suspect a memory corruption. Can you reproduce this crash? Any chance to get a valgrind log?

[Apport retracing service (apport)]

StacktraceTop:
 *__GI_raise (sig=<value optimized out>)
 *__GI_abort () at abort.c:92
 __libc_message (do_abort=<value optimized out>,
 malloc_printerr (action=3,
 *__GI___libc_free (mem=<value optimized out>)

[Omer Akram (om26er)]

closing since upstream bug closed due to lack of Valgrind logs, since the issue is not reproduce able