GNOME Bugzilla – Bug 695754
Use-after-free in source_registry_source_notify_enabled_idle_cb()
Last modified: 2014-12-12 10:36:39 UTC
I just got this crash after a password prompt for an EWS account which I only not enabled. My steps: 0) no password for the account saved in keyring a) Edit->Preferences->Mail Accounts->select the account->Edit - got a password prompt, filled in password, left [x] save to keyring b) cancel the account editor c) enable the account ---- Critical and fatal warnings logged during execution ---- ** Gtk **: gtk_entry_set_text: assertion `text != NULL' failed ** Gtk **: gtk_entry_set_text: assertion `text != NULL' failed ** Gtk **: gtk_entry_set_text: assertion `text != NULL' failed ** Gtk **: gtk_entry_set_text: assertion `text != NULL' failed ** Gtk **: gtk_entry_set_text: assertion `text != NULL' failed ** GLib-GObject **: g_object_ref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
+ Trace 231635
Thread 4 (Thread 0x7f79777fe700 (LWP 16928))
Downstream bug report from 3.8.3 about the same, also involving ews: https://bugzilla.redhat.com/show_bug.cgi?id=982892 From var_log_messages just from the crash: Jul 8 09:14:24 bigblacklinux /etc/gdm/Xsession[25398]: (evolution:26026): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed Jul 8 09:14:24 bigblacklinux /etc/gdm/Xsession[25398]: (evolution:26026): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' Jul 8 09:14:24 bigblacklinux /etc/gdm/Xsession[25398]: (evolution:26026): GLib-GObject-CRITICAL **: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed Jul 8 09:14:24 bigblacklinux /etc/gdm/Xsession[25398]: (evolution:26026): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
+ Trace 232216
Thread 1 (Thread 0x7fee49aab700 (LWP 26076))
Downstream bug report about the same from 3.10.0: https://bugzilla.redhat.com/show_bug.cgi?id=1018388 Description of problem: This happened when creating the configuration for an EWS account.
Just a "me too" - I just hit exactly this when configuring Evolution to use an EWS server (Office 365) for the first time.
I cannot reproduce it again, with the same steps I gave at comment #0.
I just had this happen to me again, being the original downstream reporter of https://bugzilla.redhat.com/show_bug.cgi?id=1018388 (that was 5 months ago!).
I managed to reproduce this. The problem was that evolution-ews created a new ESourceRegistry instance in its ews_store_maybe_update_sent_and_drafts(), which was freed quickly afterwards, but it could be that an event had been added into the ESourceRegistry's main_context, which was not flushed before dispose, thus left there some idle/timeout sources to be done on a freed ESourceRegistry. I made changes in both evolution-ews and evolution-data-server. Created commit c77dec7 in eds master (3.13.9+) [1] Created commit fc99a07 in ews master (3.13.9+) [2] Created commit fe77982 in eds evolution-data-server-3-12 (3.12.10+) Created commit 6a5a2d7 in ews evolution-ews-3-12 (3.12.10+) [1] https://git.gnome.org/browse/evolution-data-server/commit/?id=c77dec7 [2] https://git.gnome.org/browse/evolution-ews/commit/?id=fc99a07