Created attachment 275512 [details]
Offending email

This email is the one that evolution is hanging on. The other email with the two 9MB (CSV, and XML) files as /attachments/ give the same problem.

I have added the URL to fedora, where I have also reported the problem. At work it's exchange-ews, at home is a normal dovecot/IMAP server. Both cause the same problem with rendering a large email. Please fix this asap, because I cannot receive large emails... not even from anacron.

Testcase in comment 1 imported locally takes about 15 seconds to render on my six year old laptop in evolution-3.10.4-2.fc20.i686 - no problems.

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, the import didn't take any time at all. It's when I double click to open the email.

This is also filled downstream at:
https://bugzilla.redhat.com/show_bug.cgi?id=1093188

I asked there for a backtrace, which applies here as well. My guess would be that you face bug #724909.

emrecio: In case you can test, is this still a problem in Evoluion 3.12?

Yeah, this is still a problem with evolution 3.12. I have even downloaded/compiled a copy on my work desktop to no avail. Note, does running KDE as my WM make a difference? The only thing the same between the two boxes is that KDE is running as the primary window manager on both... perhaps I should try a separate user with GNOME instead??

Please install debuginfo packages for evolution-data-server and evolution, then get a backtrace of running/stuck evolution, to see what it does. You can get the backtrace with command like this:
    $ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt
Please check the bt.txt for any private information, like passwords, email address, server addresses,... I usually search for "pass" at least (quotes for clarity only).

(In reply to comment #6)
> I asked there for a backtrace, which applies here as well. My guess would be
> that you face bug #724909.

If I'm correct, then the workaround is to get rid of
   /usr/lib/evolution/3.10/modules/module-text-highlight.so
Alternatively in /usr/lib64/... or some other place, which would your distribution use.

Created attachment 280170 [details]
backtrace 3.12.2

(In reply to comment #10)
> (In reply to comment #6)
> > I asked there for a backtrace, which applies here as well. My guess would be
> > that you face bug #724909.
> 
> If I'm correct, then the workaround is to get rid of
>    /usr/lib/evolution/3.10/modules/module-text-highlight.so
> Alternatively in /usr/lib64/... or some other place, which would your
> distribution use.

I removed and still no go:
sudo mv /usr/local/lib/evolution/3.12/modules/module-text-highlight.* /tmp/

(In reply to comment #9)
> Please install debuginfo packages for evolution-data-server and evolution, then
> get a backtrace of running/stuck evolution, to see what it does. You can get
> the backtrace with command like this:
>     $ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt
> Please check the bt.txt for any private information, like passwords, email
> address, server addresses,... I usually search for "pass" at least (quotes for
> clarity only).

Note, I compiled evolution with C/CXX flags w/ "-g" and since I *had* the debuginfo packages installed for evolution 3.10 (and all its dependencies) before I uninstalled 3.10 to try out 3.12 I am assuming all debug info packages in the stack underneath should be installed.

I can recompile evolution with some other flags if "-g" is not sufficient.

Thanks in advance. I have to use alpine to read these emails.

Thanks for the update. I pasted the relevant part below. This had been reported as bug #704271 and it is some WebKit glitch.

+ Trace 233802

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