GNOME Bugzilla – Bug 358319
Crash in html_tokenizer_end at htmltokenizer.c line 1366
Last modified: 2011-09-16 11:06:44 UTC
What were you doing when the application crashed? launching Evolution Distribution: Slackware Slackware 10.2.0 Gnome Release: 2.16.0 2006-09-15 (GARNOME) BugBuddy Version: 2.16.0 Memory status: size: 128913408 vsize: 0 resident: 128913408 share: 0 rss: 39718912 rss_rlim: 0 CPU usage: start_time: 1159541244 rtime: 0 utime: 937 stime: 0 cutime:816 cstime: 0 timeout: 121 it_real_value: 0 frequency: 0 Backtrace was generated from '/home/jander/garnome/bin/evolution-2.8' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1232414496 (LWP 8707)] [New Thread -1302709328 (LWP 8900)] [New Thread -1294320720 (LWP 8899)] [New Thread -1285538896 (LWP 8834)] [New Thread -1276867664 (LWP 8804)] [New Thread -1264841808 (LWP 8803)] [New Thread -1256416336 (LWP 8757)] [New Thread -1248027728 (LWP 8751)] [New Thread -1239639120 (LWP 8750)] 0xb7421071 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 73578
Thread 1 (Thread -1232414496 (LWP 8707))
There's also an Ubuntu bug with a similar crash here: https://bugs.edge.launchpad.net/ubuntu/+source/gtkhtml3.14/+bug/256493
*** Bug 440315 has been marked as a duplicate of this bug. ***
see bug 440315 for more info
It seems like efh_format has been rescheduled and underlying GtkHML gone meanwhile, or maybe even without reschedule. Hard to say without some raw steps at the moment. Say quickly changing between HTML messages with/without images?
Downstream bug report about the same on 2.29.4: https://bugzilla.redhat.com/show_bug.cgi?id=551340 With this comment: The crash happened some time after startup of evolution. This was the first startup of evolution after I updated to rawhide from F-12. I had my inbox selected (imap) and was syncing folders with the server. At the same time the Message Preview window was open and was attempting to format the first visible message. and actual trace:
+ Trace 220040
Thread 1 (Thread 2345)
This seems to me closely related to bug #314558, thus I'm marking it as a duplicate. *** This bug has been marked as a duplicate of bug 314558 ***