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 748065 - Large CSV attachments freeze Evolution
Large CSV attachments freeze Evolution
Status: RESOLVED DUPLICATE of bug 733877
Product: evolution
Classification: Applications
Component: general
3.16.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2015-04-17 16:10 UTC by alski85
Modified: 2015-04-21 04:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description alski85 2015-04-17 16:10:16 UTC
Large CSV attachments freeze evolution completely.  The larger the CSV attachment, the longer evolution hangs for.  A 5MB csv attachment will lockup Evolution for about 40 seconds.

The preview window shows "Retrieving message" and the bottom status area reads "Parsing Message" during this time.

Evolution doesn't seem to actually crash, and running under GDB doesn't show any activity or weird looping while this is happening either.

To reproduce:
Receive an email containing a large(>5MB) .csv file
Click received message in Evolution


Please let me know what other info I can provide to track this down, it's existed for as long as I've used evolution and is a very frustrating bug.

Thank you,
Alex
Comment 1 Milan Crha 2015-04-20 11:52:26 UTC
Thanks for a bug report. I suppose you face bug #743926. Is the CSV attachment shown inline by default, or only after you expand it manually?
Comment 2 alski85 2015-04-20 14:52:00 UTC
The attachments are not shown inline by default, only after I manually click View Inline from the attachment dropdown.

Please let me know what other info may be needed.
Comment 3 Milan Crha 2015-04-21 04:27:21 UTC
Thanks for the update. In that case, attachment not expanded (shown inline) by default, you face bug #733877 (sub-bug of the bug #743926).

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