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 315344 - Random messages can crash evolution
Random messages can crash evolution
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.0.x (obsolete)
Other All
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-09-06 11:05 UTC by surak
Modified: 2005-09-30 10:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description surak 2005-09-06 11:05:59 UTC 
Steps to reproduce:
1. Open evolution, read some messages
2. Some of them may crash evolution, even when they worked before (imap folder)
- other imap clients can read this message fine
3. Move the message to another folder (using another mail app) and move it back,
it will get to work


Stack trace:
I'm sorry, I moved the last problematic message just right now and the problem
is gone for now.

Other information:
evolution printed out this at console:
GLib-ERROR **: gmem.c:141: failed to allocate 4128924623 bytes
aborting...
Comment 1 parthasarathi susarla 2005-09-06 11:37:40 UTC 
Nothing much can be done without a stack trace.
Comment 2 Christian Kirbach 2005-09-06 12:58:57 UTC 
Thanks for the bug report. Without a stack trace from the crash it's very hard 
to determine what caused it. Can you provide us with one? Please see http://
live.gnome.org/GettingTraces for more information on how to do so.
Comment 3 vivek jain 2005-09-28 05:09:12 UTC 
Yeah there used to be crashes when viewing particular mails with non
standardised format, the bugs regarding that have been fixed in 2.4 and 2.2 as
well, please update and check.
Comment 4 surak 2005-09-29 20:20:58 UTC 
No. This happens with both 2.2 and 2.4, as well as opening some images. Look at
http://bugzilla.gnome.org/show_bug.cgi?id=316516

The next time I get this I'll post a stack trace.