GNOME Bugzilla – Bug 338921
crash dislaying a mail
Last modified: 2009-01-27 04:24:15 UTC
Yeah, sorry for the lousy Summary and this description. But I really don't know what exactly triggered this. Not reproducible with that particular mail either. All I noticed was a (seemingly) lag in the network connection, somewhere. Clicked the Stop button twice, as I was tired of waiting and wanted to check the connection -- when Evo crashed. By the time bug-buddy was up, the connection definitely worked again, without any action. Thus I can't even tell if the connection really was down for a few seconds, lagged only, or if that lag affected parts of the network wich where not used by the IMAP connection at all... Evolution 2.6.0, GtkHTML 3.10.0 Including the crashing top-most thread only (entire stacktrace saved). Backtrace was generated from '/opt/gnome-2.14/bin/evolution-2.6' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1230379328 (LWP 10286)] [New Thread -1297278032 (LWP 10343)] [Thread debugging using libthread_db enabled] [New Thread -1230379328 (LWP 10286)] [New Thread -1297278032 (LWP 10343)] [Thread debugging using libthread_db enabled] [New Thread -1230379328 (LWP 10286)] [New Thread -1297278032 (LWP 10343)] [New Thread -1288701008 (LWP 10342)] [New Thread -1278919760 (LWP 10295)] [New Thread -1269449808 (LWP 10294)] [New Thread -1260651600 (LWP 10292)] [New Thread -1252222032 (LWP 10290)] [New Thread -1243829328 (LWP 10289)] [New Thread -1235436624 (LWP 10288)] 0xffffe410 in ?? ()
+ Trace 67698
*** Bug 360851 has been marked as a duplicate of this bug. ***
*** Bug 363152 has been marked as a duplicate of this bug. ***
*** Bug 369322 has been marked as a duplicate of this bug. ***
*** Bug 369910 has been marked as a duplicate of this bug. ***
*** Bug 397498 has been marked as a duplicate of this bug. ***
confirming as per dups.
*** Bug 436829 has been marked as a duplicate of this bug. ***
bug 434262 is probably a duplicate. ------- i quickly deleted messages in my pop inbox (NO hide deleted messages enabled) and moved with the up-arrow key of my keyboard. cannot reproduce the crash with that particular e-mail message, perhaps some kind of racing? evo 2.11.1, gtkhtml 3.15.1 svn. System: Linux 2.6.21-1.3142.fc7 #1 SMP Mon May 7 21:14:09 EDT 2007 i686 Memory status: size: 174473216 vsize: 174473216 resident: 49102848 share: 38969344 rss: 49102848 rss_rlim: 4294967295 CPU usage: start_time: 1179400924 rtime: 586 utime: 398 stime: 188 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/evolution-2.12' [?1034hUsing host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208551744 (LWP 27722)] [New Thread 145120144 (LWP 27752)] [New Thread 110263184 (LWP 27751)] [New Thread 131578768 (LWP 27748)] [New Thread 95525776 (LWP 27745)] [New Thread 58485648 (LWP 27743)] [New Thread 33831824 (LWP 27740)] [New Thread 70601616 (LWP 27739)] 0x0031c402 in __kernel_vsyscall ()
+ Trace 134599
Thread 1 (Thread -1208551744 (LWP 27722))
evolution crashes quite often since 2.19
seb: same here. i just have to quickly move in the message list by using the arrow keys. crashes like 3 times a day. sigh.
Hmm. I think in head, Im facing such issues after bug #338921 Im just reverting a few of them to test it. Looks like it is stable after I revert all. Im just suspecting it.
seb, can you try reverting locally and test it? It is fine for me.
Sigh. It was due to the all cool spinner animations in the preview. Im reworking and fixing it for 2.11.3 Thanks for the 'CC' andre :) I got it finally. It didn't crash at all for me, when I commented the spinner animation in the preview.
*** Bug 434262 has been marked as a duplicate of this bug. ***
*** Bug 441372 has been marked as a duplicate of this bug. ***
no need to test the reverted change then?
Seb, no need to test. I will disable the spinner in preivew for 2.11.3 and will fix it right for 2.11.4. (I dont think I have sufficient time for fixing this in 2.11.3)
evolution 2.11.3 is *much* more stable for me.
haven't been able to face this crash in the last time, running 2.11.3 and .4 here.
no duplicates since then, closing as fixed. please anybody reopen if he can reproduce this with evo 2.11.4/gtkhtml3.15.4 or higher.
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/147626 has a similar backtrace on GNOME 2.20, reopening "#0 0xb7b5e16f in update_or_redraw (ip=0x99c5028) at htmlimage.c:1093 list = (GSList *) 0x0 update = 0
+ Trace 166852
The traces seems to be right, may be due to another broken image passed. But the original bug was due to spinner.
*** Bug 494297 has been marked as a duplicate of this bug. ***
*** Bug 501310 has been marked as a duplicate of this bug. ***
*** Bug 540541 has been marked as a duplicate of this bug. ***
Note that bug #432578 (which concerns another evolution/gtkhtml crash) contains a detailed analysis of this bug in comments two (http://bugzilla.gnome.org/show_bug.cgi?id=432578#c2) through seven (http://bugzilla.gnome.org/show_bug.cgi?id=432578#c7). Those comments were made just over one and a half year ago.
Created attachment 121975 [details] [review] proposed gtkhtml patch for gtkhtml; This is quite stupid patch, but from a particular point of view makes sense. The bad thing is I'm not able to check whether it'll be better or not with the patch, because I'm not able to reproduce it. The idea behind it is that the interest in the image pointer left before the image itself has been loaded, thus the structure itself wasn't freed, because we only have the interest in the image, but nobody else, which is checkable by the 'factory' member. It's set to NULL on two places, in cleanup_images and in html_image_factory_unregister. I guess it has been set in the former function, but the structure itself has not been freed, because it is html_image_pointer_ref'ed in html_image_pointer_load.
Commit to stable/trunk
Committed to trunk. Committed revision 9043. Committed to gnome-2-24. Committed revision 9044.
*** Bug 559869 has been marked as a duplicate of this bug. ***
*** Bug 560607 has been marked as a duplicate of this bug. ***
*** Bug 560888 has been marked as a duplicate of this bug. ***
*** Bug 564703 has been marked as a duplicate of this bug. ***
*** Bug 440855 has been marked as a duplicate of this bug. ***