Description of problem: I don't know exactly but it was reproducable trying to 'Group Reply' to an email that I had initially sent Version-Release number of selected component: evolution-3.10.4-2.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: evolution crash_function: g_realloc executable: /usr/bin/evolution kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #7 g_realloc at gmem.c:169 #8 g_array_maybe_expand at garray.c:785 #9 g_array_append_vals at garray.c:423 #10 g_byte_array_append at garray.c:1665 #11 stream_mem_write at camel-stream-mem.c:131 #12 camel_stream_write at camel-stream.c:158 #13 stream_filter_write at camel-stream-filter.c:226 #14 camel_stream_write at camel-stream.c:158 #15 camel_stream_write_to_stream at camel-stream.c:306 #16 e_mail_formatter_format_text at e-mail-formatter.c:1096 Potential duplicate: bug 708852
Created attachment 908361 [details] File: backtrace
Created attachment 908362 [details] File: cgroup
Created attachment 908363 [details] File: core_backtrace
Created attachment 908364 [details] File: dso_list
Created attachment 908365 [details] File: environ
Created attachment 908366 [details] File: limits
Created attachment 908367 [details] File: maps
Created attachment 908368 [details] File: open_fds
Created attachment 908369 [details] File: proc_pid_status
Created attachment 908370 [details] File: var_log_messages
(In reply to Jamie Lennox from comment #0) > I don't know exactly but it was reproducable trying to 'Group Reply' to an > email that I had initially sent Thanks for a bug report. Do you mean that you can reproduce this reliably, with a certain message? In case you can, could you save it as mbox (right-click on it in the message list, to get the option), then send it to me directly, thus no private information is exposed?
Sorry, I don't know what the exact message was and trying the steps again on a different message seems to work as expected.
Okay, no problem. I'm closing this for now, but please feel free to reopen and provide more information in case you'll manage to reproduce this again with a certain message in the future. Thanks in advance.