Bug 207648
Summary: | Evolution locks when displaying e-mail with large tiff drawing attached | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rene van Paassen <m.m.vanpaassen> | ||||
Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||
Status: | CLOSED UPSTREAM | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 8 | CC: | mcrha | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2008-03-12 02:35:51 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Rene van Paassen
2006-09-22 08:18:08 UTC
Thanks for the bug report. As of yesterday, Evolution 2.6 is no longer supported in Fedora Core 5. Can you please try again with Evolution 2.8 in Fedora Core 6? Evolution 2.8 (on x86_64 btw) has the same problem. Created attachment 142768 [details]
9000 x 9000 points tiff file that cannot be attached to an evolution message
Played around with large tiff files with some scribbles in it. Attached 9000x9000 point file cannot be attached to message in evolution. Evolution uses some memory for the message (but not all in the machine), and then starts to eat CPU cycles only. 8500x8500 points message can be attached without problems. Problem still exists in Evolution 2.12.0. Based on my investigations, the problem is not in evolution itself, but in gdk_pixbuf_scale. I added this bug to upstream against evolution [1], because there could be done some improvement. We can move this bug either against gdk or close, even closing this will not solve this. [1] http://bugzilla.gnome.org/show_bug.cgi?id=488213 Moving upstream to the bug referenced in comment #6. Looks like there's at least a partial solution for this in 2.22. |