I have encountered a reproducible crash in Evolution, triggered by the
attempted import of a large (in this case 359.1 MB) mbox file.

Steps to reproduce:

1) Launch evolution normally.
2) Select File -> Import
3) Click "Forward"
4) Select "Import a single file"
5) Click the drop-down item marked "File:"
6) In the resulting dialog, select the offending mbox.
7) Click "Open"

After step #7, the interface will freeze for approximately 10-15 seconds,
after which evolution will terminate.

The following is written to stdout upon termination:

"
GLib-ERROR **: /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmem.c:176: failed to allocate 536870912 bytes
aborting...
Aborted
"

The machine on which I have encountered this has plenty of free real memory
(3GB total, well over 1GB free at the time of the crash) in addition to 2GB
of unused swap, so I don't think it's an issue of resource exhaustion.

Please let me know if anything else is needed.

A backtrace (as reportbug should have told you, did it?). And it will be
really faster if you also report upstream directly.

It might help to provide the relevant mbox, though 350M of private mail
won't exactly be easy to provide I guess.

Cheers,

Sorry about that. I'm still rather new at bug-reporting.  I've attached a
backtrace to this message.

You're right -- attaching the mbox in question isn't really an option for a
couple reasons.

Since I can't reproduce the crash with some of the smaller mbox files I have,
I'm assuming it's size-dependent.

Cheers,
Rob

Hmhm, I see nothing evolution-related in this backtrace. It might be
worth trying something like:

thread apply all backtrace full

in gdb.

It might be related to some mail too, thought the errors message seem to
lead to a memory size too large indeed.

I don't think it has anything to do with the contents, as I was able to
reproduce the crash by importing another similarly-sized (but entirely
different) mbox.