GNOME Bugzilla – Bug 603199
Crash in html_object_split()
Last modified: 2014-12-02 01:05:44 UTC
What were you doing when the application crashed? Distribution: Debian squeeze/sid Gnome Release: 2.28.0 2009-10-27 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.31-1-686 #1 SMP Sun Nov 15 20:39:33 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Amaranth GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 241369088 vsize: 241369088 resident: 85135360 share: 26853376 rss: 85135360 rss_rlim: 18446744073709551615 CPU usage: start_time: 1259333112 rtime: 15208 utime: 10413 stime: 4795 cutime:29 cstime: 29 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb3daeb70 (LWP 4263)] [New Thread 0xad92cb70 (LWP 4262)] [New Thread 0xae1fab70 (LWP 3955)] [New Thread 0xb01feb70 (LWP 3954)] [New Thread 0xb1efbb70 (LWP 3945)] [New Thread 0xb36feb70 (LWP 3941)] [New Thread 0xb4850b70 (LWP 3937)] [New Thread 0xb5051b70 (LWP 3936)] 0xb77e3424 in __kernel_vsyscall ()
+ Trace 219338
Thread 1 (Thread 0xb5a4c760 (LWP 3926))
A debugging session is active. Inferior 1 [process 3926] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ** evolution **: atk_object_set_name: assertion `name != NULL' failed ----------- .xsession-errors --------------------- (firefox-bin:7554): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:7554): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:7554): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:7554): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:7554): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:7554): Gdk-WARNING **: XID collision, trouble ahead ** gtkhtml:ERROR:htmlobject.c:939:html_object_split: assertion failed: (self) restoring draft flag 'text/plain' --------------------------------------------------
Good stack trace but no reproducer. GtkHTML issue.
Similar downstream bug report from evolution 3.2.1 (gtkhtml 4.2.1): https://bugzilla.redhat.com/show_bug.cgi?id=749339 libreport version: 2.0.6 abrt_version: 2.0.4.981 backtrace_rating: 4 cmdline: evolution comment: It was receiving emails from an imap server. Nothing fancy just downloading and checking for new email once in a while. crash_function: split executable: /usr/bin/evolution kernel: 3.1.0-0.rc10.git0.1.fc16.x86_64 reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) time: Wed Oct 26 20:17:23 2011
+ Trace 228918
Thread 1 (Thread 0x7fdd6f2d1980 (LWP 7900))
I'll have to check but I believe I was able to reproduce it on my machine yesterday.
Since version 3.6, Evolution uses WebKit instead of GtkHtml for displaying messages. (And for completeness, Evolution 3.14 is planned to use WebKit also for composing and editing messages so GtkHtml will not receive any fixes anymore.) Hence I am closing this GtkHtml rendering bug report. We are sorry that your request was not handled in time when it was reported but unfortunately manpower is very limited (and does not allow testing every single reported issue separately again either). Please feel free to reopen this report (and move it to the "Evolution" product and the "Mail" component) if the problem described in this bug report still happens in a recent supported Evolution version which uses WebKit (the current stable Evolution version is 3.12).