GNOME Bugzilla – Bug 750048
Geary crashes when interacting with a specific email
Last modified: 2016-08-02 01:17:01 UTC
Created attachment 304186 [details] Offending Email Geary crashes when I view a specific email and then attempt to one of the following actions. Archive, Delete, View different email/account. The email's sources is attached, as well as a stack trace.
Created attachment 304187 [details] Stack trace
Thanks. Unfortunately, all I can get from that stacktrace is that something's gone wrong inside webkit. I'm unable to reproduce the crash on my machine. What version of Geary are you running? What version of WebKitGTK do you have? Did you load the remote images?
Geary: 0.10.0 Webkitgtk: 2.4.9-1 I did not load the remote images. Would it be helpful if I forwarded the email to do for you to try and recreate it?
(In reply to Marc Thomas from comment #3) > Geary: 0.10.0 > Webkitgtk: 2.4.9-1 Thanks. I'm running webkitgtk 2.4.8, so that could account for the difference > Would it be helpful if I forwarded the email to do for you to try and > recreate it? I've sent it to myself, and that didn't cause a problem. Since the problem seems to be in webkit, I assume it's caused by the body and not the headers. Since it happens when removing the email from the conversation viewer, my suspicion is that something's going wrong inside of Webkit as is destroys the email. Frankly, at this point the best course of action is probably just to delete the offending email and keep a watch out for it happening again. If it does, we can try to find some commonality between the emails to get a better idea of what's going wrong.
This same issue occurred for me as well on Geary 0.10.0 today. One particular email causes Geary to segfault and crash every time I attempt to Archive or Delete. The resulting error is: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff46ce9b4 in WebCore::RenderBlockFlow::removeFloatingObject(WebCore::RenderBox&) () from /lib64/libwebkitgtk-3.0.so.0 (gdb) backtrace full
+ Trace 235815
I have included the stack trace (geary.gdb) when replicating this event. However, I could not generate a backtrace. The following message is returned on '(gdb) backtrace full': No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7fffffffcac8
Created attachment 317458 [details] stack trace
Marking this as a duplicate of Bug 769010 instead of vice-versa since the stack trace there is filled out a bit better. *** This bug has been marked as a duplicate of bug 769010 ***