Bug 1093188

Created attachment 891296 [details]
source code where it loops

I have confirmed that this happens with a plain text email of 9MB. The email came from a process running under anacron. The server was not EWS but a standard dovecot IMAP server. See attached

Created attachment 891590 [details]
mbox format of email that hangs evolution

this is the mbox format that you can append to your mailspool file, which would hang evolution.

I downloaded the file, and decompressed it, and it has been 60 seconds and
still no email. It just freezes on me. I imported it into my imap/dovcot
servers' inbox. I am running a relatively modern (2009 Compaq CQ60, dual 2GHz,
64-bit System) The same thing happens on my intel i5 at work with 10GB RAM i686
with PAE. Same version, same Fedora 20. I am running KDE as my default desktop.
I installed from the NetInstall and selected KDE only as my desktop. Note, that the import takes no time at all, it's when I double click to open the email. Since I started writing this it now has been 2 minutes, and one of my cores are still at 100%

Thanks for a bug report. Despite similar summary, this bug report has nothing to do with bug #97232, evolution evolved between those 10 years in many ways, so it's not the same thing by any means.

By the way, why do you fill this both upstream and here? It doubles the work, for you, for me, for everyone.

The important part is backtrace. Please install debuginfo package for evolution and then run it under gdb like this:

   $ gdb evolution --ex r --ex "t a a bt" --ex q

then, when it gets stuck, switch to the gdb terminal and Ctrl+C it. It'll print the backtrace of it, showing what the evolution does at that moment. Then it'll quit gdb (and closes the evolution), if you confirm it.

If I may wild-guess from the information you gave, then this is bug #1089966. But I need your confirmation first, either by trying the workaround or (preferably) by providing the backtrace.

The work around seems to be OK for the preview pane, but not when I double click on the message to open it in a new window (strange!)

I then killed and restarted evolution, but this time disabled the preview pane. I then double clicked on the email, with the same hanging results.

I want to spare room for debuginfo files on this laptop. I will try tomorrow from the similarly affected machines at work to get the gdb output.

note, I compile evolution 3.12.1 on my work box, and same thing happens. See the backtraces.

Created attachment 894190 [details]
backtrace of evolution

(In reply to Elmo from comment #6)
> I then killed and restarted evolution, but this time disabled the preview
> pane. I then double clicked on the email, with the same hanging results.

Makes sense, the extra window has always preview panel on, otherwise the window would be empty.

(In reply to Elmo from comment #7)
> note, I compile evolution 3.12.1 on my work box, and same thing happens. See
> the backtraces.

If I read the backtrace properly, then evolution is showing a message to you, namely:
 "Cannot start Evolution.  Another Evolution instance may be unresponsive.
  System error: ..."

It might be as it says, there is another 'evolution' process running in the background (ps ax | grep evolution), or some other issue happened. As you didn't get that far in this evolution instance, to select the offending message, then I'm sure this backtrace is unrelated.

Rather than trying to compile evolution from sources, what about downloading only debuginfo packages and install them? The backtrace shows lack of debug information anyway. The debuginfo packages for evolution itself can be found here, just pick that evolution-debuginfo, which is for your architecture:
   http://koji.fedoraproject.org/koji/buildinfo?buildID=500933

I suggest this, because I suppose the problem when opening self-compiled evolution could be caused by missing dependencies, and/or inability to contact the services over D-Bus.

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

I have what I think is the same problem with Evolution. I received a text message with 3 attachments - one HTML, one XML and one PDF. Total size is 1.6MB. Evolution hangs just trying to see the initial text message (which is just a few lines long).

I am running Fedora 20 and the following packages:

evolution-3.10.4-3.fc20.x86_64
evolution-data-server-3.10.4-4.fc20.x86_64
evolution-ews-3.10.4-1.fc20.x86_64
highlight-3.18-1.fc20.x86_64

I can confirm that the workaround mentioned in comment #5 (from bug #1089966) seems to work fine.

As requested in comment #5 I installed the evolution debuginfo packages, and ran the dbg command specified. Attached is the dbg backtrace produced when I hit control-c.

If you need more information, or help with testing something, then let me know.

Created attachment 936630 [details]
dbg backtrace of evolution

dbg backtrace as mentioned in comment #5.

Thanks for the update. gdb failed to get the backtrace:
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.

but as you described your testing it can be that this is the same issue as
bug #1089966. I'm not sure why you wrote it here, though.

Anyway, it was not easy (almost possible) to backport the upstream change due to other API changes being involved, but there was a change upstream which makes things simpler, thus I'll try to backport the fix into Fedora 20. I mean the change for bug #1089966.

I'm moving this bug report to webkitgtk3, where it actually belongs.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.