Bug 1306627 - freeze when rendering inline attachments of the attached message
Summary: freeze when rendering inline attachments of the attached message
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Milan Crha
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-11 13:27 UTC by Matěj Cepl
Modified: 2016-02-11 16:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-11 16:47:24 UTC
Target Upstream Version:

Attachments (Terms of Use)
test case email (12.99 MB, application/mbox)
2016-02-11 13:27 UTC, Matěj Cepl 		no flags Details
backtrace (13.31 KB, text/plain)
2016-02-11 13:28 UTC, Matěj Cepl 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Matěj Cepl 2016-02-11 13:27:10 UTC 
Created attachment 1123143 [details]
test case email

Description of problem:
When switching "View All Attachments inline" Evolution freezes.

Version-Release number of selected component (if applicable):
evolution-3.12.11-15.el7.x86_64

How reproducible:
happened twice out of two attempts

Steps to Reproduce:
1.look at the attached message in Evolution INBOX
2.switch on "View All Inline" attachments
3.

Actual results:
freeze (see attached backtrace)

Expected results:
give it a moment, but see all attachments inlined, or get some progress warnings that it takes more time

Additional info:
Comment 1 Matěj Cepl 2016-02-11 13:28:42 UTC 
Created attachment 1123144 [details]
backtrace
Comment 3 Matěj Cepl 2016-02-11 16:47:24 UTC 
After a long long time the message got parsed. So, it is a bloody inconvenient, that we don't have any progress warning or something, but it is probably not a bug worthy of RHEL.
Comment 4 Milan Crha 2016-02-11 16:49:36 UTC 
Thanks for a bug report, data and backtrace. It's a ~12MB message attachment, which the WebKitGTK+ is processing, as shown in the backtrace. There is currently nothing we can do about it. Once evolution ports to WebKit2 (that'll be in RHEL8, if everything will go smoothly), then this will be fixed on its own.
Note You need to log in before you can comment on or make changes to this bug.