GNOME Bugzilla – Bug 794693
Crash when trying to view email message source
Last modified: 2018-04-10 14:14:01 UTC
webkitgtk4-2.18.6-1.fc27.x86_64 evolution-3.26.6-1.fc27.x86_64 evolution-data-server-3.26.6-1.fc27.x86_64 gtk3-3.22.26-2.fc27.x86_64 (evolution:19369): evolution-mail-CRITICAL **: mail_reader_display_load_changed_cb: assertion 'E_IS_MAIL_READER (reader)' failed (evolution:19369): Gtk-CRITICAL **: gtk_action_set_sensitive: assertion 'GTK_IS_ACTION (action)' failed (evolution:19369): Gtk-CRITICAL **: gtk_action_set_sensitive: assertion 'GTK_IS_ACTION (action)' failed (evolution:19369): GLib-GObject-WARNING **: invalid unclassed pointer in cast to 'GtkWidget' (evolution:19369): Gtk-CRITICAL **: gtk_widget_get_visible: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:19369): evolution-util-CRITICAL **: e_web_view_update_highlights: assertion 'E_IS_WEB_VIEW (web_view)' failed (evolution:19369): GLib-GObject-WARNING **: invalid unclassed pointer in cast to 'GObject' (evolution:19369): GLib-GObject-CRITICAL **: g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failed Thread 1 "evolution" received signal SIGSEGV, Segmentation fault. mail_reader_load_changed_cb (reader=0x55555916c5d0, event=<optimized out>, display=0x555559baf550 [EMailDisplay]) at /usr/src/debug/evolution-3.26.6-1.fc27.x86_64/src/mail/e-mail-reader.c:2920
Created attachment 370146 [details] stacktrace
Thanks for a bug report. I suppose it's an up-to-today F27 without updates-testing in GNOME under Wayland, right? The first runtime warning might have the clue. The rest can be just due to it. Incorporate G_SLICE=always-malloc ideally. I cannot run evolution under GNOME with Wayland here, due to mesa-dri-drivers-17.3.6-1.fc27.x86_64 update, thus I downgraded it to: mesa-dri-drivers.x86_64 17.2.2-4.fc27 which downgraded also mesa-filesystem.x86_64 17.2.2-4.fc27 I do not see any such runtime warnings, neither the crash, after pressing View->Message Source from the menu of Evolution when run in GNOME under Wayland with those package versions.
Created attachment 370149 [details] output of "G_SLICE=always-malloc valgrind --num-callers=30 evolution" Here: mesa-dri-drivers-17.3.6-1.fc27, mesa-filesystem-17.3.6-1.fc27. "G_SLICE=always-malloc valgrind --num-callers=30 evolution" gets me a SIGSEGV.
Created attachment 370150 [details] output of "G_SLICE=always-malloc valgrind --num-callers=30 evolution" This time the correct file.
This is on Wayland.
Interesting. Cannot reproduce anymore.
I've been able to reproduce similar crash. For me, the window which was supposed to show the message source had been closed before it had been populated, with some ongoing operations in the background (like in the idle queue), and when they elapsed they used already freed objects, which could lead at least to some runtime warnings and in some cases also to the crash. I've seen it in the same functions as is shown in your valgrind long, similarly with the runtime warnings (I've got even more of them), thus I believe it's that issue. Created commit 913472df2c in evo master (3.29.1+) Created commit c4ada09c6e in evo gnome-3-28 (3.28.1+)
*** Bug 795119 has been marked as a duplicate of this bug. ***