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 705705 - Evo unresponsive on a specific message
Evo unresponsive on a specific message
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
3.8.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 752511 766197 (view as bug list)
Depends on:
Blocks: 733877
 
 
Reported: 2013-08-08 22:57 UTC by Patrick OCallaghan
Modified: 2021-05-31 13:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
mbox file which breaks Evo (261.78 KB, message/conmpressed)
2013-08-08 23:04 UTC, Patrick OCallaghan
Details

Description Patrick OCallaghan 2013-08-08 22:57:56 UTC
I have a specific message from the Fedora Test list for which seems to
make Evolution freeze. It's a fairly long text message (no HTML) in
UTF-8, Base-64 encoded. I can read it on Gmail with no problem, but Evo
starts burning up cpu and becomes unresponsive. I end up having to kill
it. This is repeatable. Other similar messages don't have this problem.

For the record, evolution-3.8.4-2.fc19.i686, Fedora 19 updated, KDE 4.10.

I saved the message in question as an mbox file, see the attachment.
Comment 1 Patrick OCallaghan 2013-08-08 23:04:01 UTC
Created attachment 251215 [details]
mbox file which breaks Evo

Message taken from the Fedora Test list.
Comment 2 Milan Crha 2013-08-09 04:33:40 UTC
Tomas, could you have a brief look, please? As I wrote in a thread [1], it doesn't happen to me always, but it does for sure.

[1] https://mail.gnome.org/archives/evolution-list/2013-August/msg00045.html
Comment 3 awilliam 2013-08-09 12:51:49 UTC
I was able to import it, but yep, I cannot view the message;  Evolution takes over a core and spins.

evolution-data-server-3.8.2-1.5.x86_64
evolution-3.8.2-1.1.x86_64
evolution-data-server-lang-3.8.2-1.5.noarch
libgtkhtml-editor-4_0-0-4.6.5-1.1.x86_64
libgtkhtml-4_0-0-4.6.5-1.1.x86_64
libwebkitgtk-1_0-0-2.0.2-1.1.x86_64
webkit2gtk-3_0-injected-bundles-2.0.2-1.3.x86_64
libwebkit2gtk-3_0-25-2.0.2-1.3.x86_64
libwebkitgtk2-lang-2.0.2-1.1.noarch
libwebkitgtk-3_0-0-2.0.2-1.3.x86_64
Comment 4 Reid Thompson 2013-08-09 13:13:34 UTC
evo 3.9.90 git head built 2013/08/05.

imported into mailder store, loads and displays fine, load takes a few seconds ( msg listed as 2.9MB on by box).  Clicking from this email to others and back several times shows no ill effects as yet.

copied msg to EWS store. loads and displays fine, load takes a few seconds ( msg listed as 2.9MB on by box).  Clicking from this email to others and back several times shows no ill effects as yet.

glib
  2-33-10
* 2-37-4
  glib-2-32
  glib-2-34
  master

libgweather
* master

glib-networking
  2-33-10
  glib-2-30
* master

libsoup
  gnome-3-6
* master

evolution-data-server
* master

gtkhtml
* master

evolution
* master

evolution-ews
* master

dconf
* master
Comment 5 Milan Crha 2015-04-22 20:09:03 UTC
This is still reproducible with webkitgtk3-2.4.8-2.fc21.x86_64. Bug #733877 has the same backtrace (pasted below from my current run with the above test message). It is in turn bug #743926, where is a link to webkit's bug
https://bugs.webkit.org/show_bug.cgi?id=143868

Thread 1 (Thread 0x7fe1a56c6a40 (LWP 8520))

  • #0 WebCore::Style::attachRenderTree(WebCore::Element&, WTF::PassRefPtr<WebCore::RenderStyle>)
  • #1 WebCore::Style::attachChildren(WebCore::ContainerNode&)
  • #2 WebCore::Style::attachRenderTree(WebCore::Element&, WTF::PassRefPtr<WebCore::RenderStyle>)
  • #3 WebCore::Style::attachChildren(WebCore::ContainerNode&)
  • #4 WebCore::Style::attachRenderTree(WebCore::Element&, WTF::PassRefPtr<WebCore::RenderStyle>)
  • #5 WebCore::Style::attachChildren(WebCore::ContainerNode&)
  • #6 WebCore::Style::attachRenderTree(WebCore::Element&, WTF::PassRefPtr<WebCore::RenderStyle>)
  • #7 WebCore::Style::resolveTree(WebCore::Element&, WebCore::Style::Change)
  • #8 WebCore::Style::resolveTree(WebCore::Document&, WebCore::Style::Change)
  • #9 WebCore::Document::recalcStyle(WebCore::Style::Change)
  • #10 WebCore::Document::updateStyleIfNeeded()
  • #11 WebCore::Document::finishedParsing()
  • #12 WebCore::HTMLDocumentParser::prepareToStopParsing()
  • #13 WebCore::HTMLDocumentParser::finish()
  • #14 WebCore::DocumentWriter::end()
  • #15 WebCore::DocumentLoader::finishedLoading(double)
  • #16 WebCore::CachedResource::checkNotify()
  • #17 WebCore::CachedRawResource::finishLoading(WebCore::ResourceBuffer*)
  • #18 WebCore::SubresourceLoader::didFinishLoading(double)
  • #19 WebCore::readCallback(_GObject*, _GAsyncResult*, void*)
  • #20 async_ready_callback_wrapper
    at ginputstream.c line 523
  • #21 g_task_return_now
    at gtask.c line 1077
  • #22 complete_in_idle_cb
    at gtask.c line 1086
  • #23 g_main_context_dispatch
    at gmain.c line 3111
  • #24 g_main_context_dispatch
    at gmain.c line 3710
  • #25 g_main_context_iterate
    at gmain.c line 3781
  • #26 g_main_loop_run
    at gmain.c line 3975
  • #27 gtk_main
    at gtkmain.c line 1207
  • #28 main
    at main.c line 638

Comment 6 Nirbheek Chauhan 2015-06-02 09:23:42 UTC
Till this bug is fixed, could Evolution not try to show the attachment preview above a certain size? This bug makes Evolution unusable as soon as you receive a plain text attachment above a certain size (~50-100KB).

The only workaround is killall -9, turn off message preview, save as mbox, extract the attachment manually with an external editor + base64 decode, then "Remove attachments" from the email so it never happens again. Hardly a series of steps one would expect the user of a mail client to do.
Comment 7 Milan Crha 2015-07-22 15:45:08 UTC
*** Bug 752511 has been marked as a duplicate of this bug. ***
Comment 8 Milan Crha 2016-05-11 07:53:59 UTC
*** Bug 766197 has been marked as a duplicate of this bug. ***
Comment 9 André Klapper 2021-05-19 12:27:31 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org (resources are unfortunately quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new bug report ticket at
  https://gitlab.gnome.org/GNOME/evolution/-/issues/

Thank you for your understanding and your help.