GNOME Bugzilla – Bug 267899
Crash on shutdown
Last modified: 2006-11-08 23:49:25 UTC
The address book sometimes crashes on evo shutdown, because the free'd AddressbookView is getting signals from its collection of EABViews. This indicates that the EABViews are not disposed when they should be. ==18541== Invalid memory access of size 4 ==18541== at 0x59ABBB88: set_folder_bar_message (addressbook-view.c:313) ==18541== by 0x560BAAD5: g_cclosure_marshal_VOID__POINTER (gmarshal.c:601) ==18541== by 0x560A8BB5: g_closure_invoke (gclosure.c:437) ==18541== by 0x560B9D35: signal_emit_unlocked_R (gsignal.c:2435) ==18541== by 0x560B8E25: g_signal_emit_valist (gsignal.c:2194) ==18541== by 0x560B90D6: g_signal_emit (gsignal.c:2238) ==18541== by 0x59ADA661: emit_folder_bar_message (e-addressbook-view.c:1298) ==18541== by 0x560BAAD5: g_cclosure_marshal_VOID__POINTER (gmarshal.c:601) ==18541== by 0x560A8BB5: g_closure_invoke (gclosure.c:437) ==18541== by 0x560B9D35: signal_emit_unlocked_R (gsignal.c:2435) ==18541== by 0x560B8E25: g_signal_emit_valist (gsignal.c:2194) ==18541== by 0x560B90D6: g_signal_emit (gsignal.c:2238) ==18541== Address 0x5977E5CC is 12 bytes inside a block of size 164 free'd ==18541== at 0x55022B75: free (vg_replace_malloc.c:231) ==18541== by 0x56102119: g_free (gmem.c:186) ==18541== by 0x560BE6D0: g_type_free_instance (gtype.c:1635) ==18541== by 0x560AABC0: g_object_last_unref (gobject.c:580) ==18541== by 0x59ABD0BE: destroy_callback (addressbook-view.c:1063) ==18541== by 0x560AD1E8: weak_refs_notify (gobject.c:1464) ==18541== by 0x560EF0E1: g_data_set_internal (gdataset.c:246) ==18541== by 0x560EE0AD: g_datalist_id_set_data_full (gdataset.c:380) ==18541== by 0x560AAB2E: g_object_real_dispose (gobject.c:530) ==18541== by 0x55D13572: ??? (gtkobject.c:381) ==18541== by 0x55DD4FA1: ??? (gtkwidget.c:6382) ==18541== by 0x560AACBC: g_object_run_dispose (gobject.c:602)
*** bug 267911 has been marked as a duplicate of this bug. ***
Reassigning bugs that no longer belong to me.
at least retargetting from 2.2 to 2.5
changing target milestone from 2.5 to future. sorry, too many bugs, too less time.
No longer seeing this, pretty sure it's been fixed.