Original report: https://bugzilla.gnome.org/show_bug.cgi?id=643097 It seems that Pochu's empathy-auth-client crashes because of tp_g_signal_connect_object See https://bugzilla.gnome.org/page.cgi?id=trace.html&trace_id=226078 for the trace Valgrind hits the error: ==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.
There is a similar natty crash with some duplicates on https://bugs.launchpad.net/ubuntu/+source/telepathy-glib/+bug/726842, the issue seem to happen when connection on empathy start of when reconnecting later on
Pochu didn't experience this issue since a while and the Ubuntu bug ( https://bugs.launchpad.net/ubuntu/+source/telepathy-glib/+bug/726842 ) didn't get new dups either. I spent a lot of time trying to debug this, tried to write a test reproducing Empathy's behaviour and it worked fine. So, I'm closing this bug for now but please reopen if you experience it with a recent Empathy / tp-glib.
That was actually a very stupid Empathy bug: https://bugzilla.gnome.org/show_bug.cgi?id=655788
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.