GNOME Bugzilla – Bug 369696
crash in Evolution: Looking at an email with...
Last modified: 2007-08-24 15:39:06 UTC
What were you doing when the application crashed? Looking at an email with a plain text attachment with 19689 lines. I hid the attachment, which was displayed in the message view. Then I switched message folders, and Evolution crashed. Usually Evolution just slows to a crawl when dealing with messages like this. It's the first time I've seen it crash. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 204107776 vsize: 0 resident: 204107776 share: 0 rss: 94281728 rss_rlim: 0 CPU usage: start_time: 1162505482 rtime: 0 utime: 1549 stime: 0 cutime:1506 cstime: 0 timeout: 43 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1233373520 (LWP 15425)] [New Thread -1283458144 (LWP 15441)] [New Thread -1273500768 (LWP 15438)] [New Thread -1256039520 (LWP 15434)] [New Thread -1247106144 (LWP 15433)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 82092
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks! [1] debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue. For some yet unknown reason, such stacktraces are pretty common currently on certain distros. However, almost all of them do turn out to be filed already, once we managed to gather a useful stacktrace. To do so, simply install the corresponding debugging packages and reproduce the issue, if possible. The resulting stacktrace (see bug-buddy details) will help us to identify and fix the issue. Just in case you ever can reproduce this crash later, please consider installing debugging packages [1] and either reopen this bug report or simply file a new one with the resulting stacktrace. Thanks! Closing this bug report as no further information has been provided. Also, please feel free to report any further bugs you find. Thanks!
I installed the debugging libraries and sent myself an email with a plain text attachment with 19689 lines. See Bug 374793. I'm pretty disappointed that you closed this without bothering to test it or confirm it yourself. I can understand not following up on it, but closing it, when it's something that can bring your app to its knees on a standard Ubuntu install is irresponsible.
Created attachment 76501 [details] A text file with 19689 lines A text file with 19689 lines. Unzip it, attach it to an email message, and send it to Evolution.
Could be related to bug 363576 I tried to reproduce it with you file and my Evo didn't crash. Which Spamfilter plugins do you have enabled?
I'm guessing I had spamassassin enabled at the time.