After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 779373 - Crash on message delete
Crash on message delete
Status: RESOLVED DUPLICATE of bug 769010
Product: geary
Classification: Other
Component: general
0.11.x
Other Linux
: High critical
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-02-28 16:49 UTC by parasit
Modified: 2017-03-05 14:51 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Backtrace (45.01 KB, text/plain)
2017-02-28 16:49 UTC, parasit 		Details
Problematic email (9.57 KB, message/rfc822)
2017-02-28 16:50 UTC, parasit 		Details

Description parasit 2017-02-28 16:49:43 UTC 
Created attachment 346918 [details]
Backtrace

Hello,
I have one (and only one, first in mailbox) message in my Inbox, wchich i CAN'T remove. When i try, application freezes, then, after couple seconds crash.
Its "normal" spam message with HTML, but I suspect that the problem is not the message itself

In attachment is GDB backtrace and problematic email, i don't have idea what else can be usefull in this case.
Comment 1 parasit 2017-02-28 16:50:31 UTC 
Created attachment 346919 [details]
Problematic email

Problematic email
Comment 2 André Klapper 2017-03-01 15:51:55 UTC 
Thanks for taking the time to report this.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols (for webkitgtk3, glib2, geary)? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so and reopen this bug report. Thanks in advance!
Comment 3 Michael Gratton 2017-03-05 14:51:35 UTC 
This looks like a duplicate of Bug 769010. Unfortunately there are some corner cases that we can't fix and this may well be one of them.

The good news is that this issue will be completely fixed in 0.12, when that is released.

*** This bug has been marked as a duplicate of bug 769010 ***