GNOME Bugzilla – Bug 643097
empathy-auth-client crash
Last modified: 2011-08-02 11:12:19 UTC
I'm getting empathy-auth-client crashes from time to time on 2.33.x. No warnings before the crash. Program received signal SIGSEGV, Segmentation fault. object_remove_closure (data=0x73e450, closure=0x6b9940) at /tmp/buildd/glib2.0-2.28.1/./gobject/gobject.c:3323 3323 /tmp/buildd/glib2.0-2.28.1/./gobject/gobject.c: No such file or directory. in /tmp/buildd/glib2.0-2.28.1/./gobject/gobject.c (gdb) bt
+ Trace 226078
Humm that looks like a tp_g_signal_connect_object() issue :\ Any chance you could get a valgrind log?
Yep. Is this useful? emilio@marte:~$ EMPATHY_PERSIST=1 XDG_DATA_DIRS=/opt/empathy/share/:/usr/share/ G_SLICE=debug-blocks G_DEBUG=gc-friendly valgrind --tool=memcheck /opt/empathy/libexec/empathy-auth-client ==17345== Memcheck, a memory error detector ==17345== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==17345== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info ==17345== Command: /opt/empathy/libexec/empathy-auth-client ==17345== ==17345== Invalid read of size 4 ==17345== at 0xC4860A6: object_remove_closure (gobject.c:3323) ==17345== by 0xC483F6C: g_closure_invalidate (gclosure.c:268) ==17345== by 0xC483D3C: g_closure_unref (gclosure.c:588) ==17345== by 0xC495A35: handler_unref_R (gsignal.c:637) ==17345== by 0xC495BF6: g_signal_handler_disconnect (gsignal.c:2389) ==17345== by 0x8A88432: observer_destroyed_cb (util.c:934) ==17345== by 0xC485ACF: weak_refs_notify (gobject.c:2231) ==17345== by 0xCCFAC81: g_datalist_clear (gdataset.c:215) ==17345== by 0xC486479: g_object_unref (gobject.c:2697) ==17345== by 0xC48414D: g_closure_invoke (gclosure.c:767) ==17345== by 0xC49C656: signal_emit_unlocked_R (gsignal.c:3252) ==17345== by 0xC49DCD5: g_signal_emit_valist (gsignal.c:2983) ==17345== Address 0x8 is not stack'd, malloc'd or (recently) free'd ==17345== ==17345== ==17345== Process terminating with default action of signal 11 (SIGSEGV) ==17345== Access not within mapped region at address 0x8 ==17345== at 0xC4860A6: object_remove_closure (gobject.c:3323) ==17345== by 0xC483F6C: g_closure_invalidate (gclosure.c:268) ==17345== by 0xC483D3C: g_closure_unref (gclosure.c:588) ==17345== by 0xC495A35: handler_unref_R (gsignal.c:637) ==17345== by 0xC495BF6: g_signal_handler_disconnect (gsignal.c:2389) ==17345== by 0x8A88432: observer_destroyed_cb (util.c:934) ==17345== by 0xC485ACF: weak_refs_notify (gobject.c:2231) ==17345== by 0xCCFAC81: g_datalist_clear (gdataset.c:215) ==17345== by 0xC486479: g_object_unref (gobject.c:2697) ==17345== by 0xC48414D: g_closure_invoke (gclosure.c:767) ==17345== by 0xC49C656: signal_emit_unlocked_R (gsignal.c:3252) ==17345== by 0xC49DCD5: g_signal_emit_valist (gsignal.c:2983) ==17345== If you believe this happened as a result of a stack ==17345== overflow in your program's main thread (unlikely but ==17345== possible), you can try to increase the size of the ==17345== main thread stack using the --main-stacksize= flag. ==17345== The main thread stack size used in this run was 8388608. ==17345== ==17345== HEAP SUMMARY: ==17345== in use at exit: 1,008,491 bytes in 10,091 blocks ==17345== total heap usage: 1,884,572 allocs, 1,874,481 frees, 82,608,979 bytes allocated ==17345== ==17345== LEAK SUMMARY: ==17345== definitely lost: 524 bytes in 16 blocks ==17345== indirectly lost: 65,864 bytes in 1,578 blocks ==17345== possibly lost: 194,163 bytes in 2,151 blocks ==17345== still reachable: 747,940 bytes in 6,346 blocks ==17345== suppressed: 0 bytes in 0 blocks ==17345== Rerun with --leak-check=full to see details of leaked memory ==17345== ==17345== For counts of detected and suppressed errors, rerun with: -v ==17345== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 10 from 6) Killed
That really sounds like a tp-glib bug so I opened https://bugs.freedesktop.org/show_bug.cgi?id=34707 Do you have a scenario to reproduce this crash? I never experienced it so it would be nice if you could try to solve it.
Haven't seen this in a while, fwiw.
Did someone experience this crash with 3.0?
*** Bug 651659 has been marked as a duplicate of this bug. ***
*** Bug 652254 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 655788 ***