Bug 1108975

Summary: [abrt] evolution: g_realloc(): evolution killed by SIGABRT
Product: [Fedora] Fedora Reporter: Jamie Lennox <jlennox>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: fabiano, jlennox, lucilanga, mbarnes, mcrha, nkinder
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4f5106b02a9764f9cbd58bb0d5833c1c3da0e3fc
Whiteboard: abrt_hash:64a91fcaf4d83fd3986a738e5f5804bfb7a950a9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-02 07:50:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jamie Lennox 2014-06-13 03:27:40 UTC 
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
Comment 1 Jamie Lennox 2014-06-13 03:27:50 UTC 
Created attachment 908361 [details]
File: backtrace
Comment 2 Jamie Lennox 2014-06-13 03:27:53 UTC 
Created attachment 908362 [details]
File: cgroup
Comment 3 Jamie Lennox 2014-06-13 03:27:58 UTC 
Created attachment 908363 [details]
File: core_backtrace
Comment 4 Jamie Lennox 2014-06-13 03:28:03 UTC 
Created attachment 908364 [details]
File: dso_list
Comment 5 Jamie Lennox 2014-06-13 03:28:07 UTC 
Created attachment 908365 [details]
File: environ
Comment 6 Jamie Lennox 2014-06-13 03:28:10 UTC 
Created attachment 908366 [details]
File: limits
Comment 7 Jamie Lennox 2014-06-13 03:28:17 UTC 
Created attachment 908367 [details]
File: maps
Comment 8 Jamie Lennox 2014-06-13 03:28:21 UTC 
Created attachment 908368 [details]
File: open_fds
Comment 9 Jamie Lennox 2014-06-13 03:28:25 UTC 
Created attachment 908369 [details]
File: proc_pid_status
Comment 10 Jamie Lennox 2014-06-13 03:28:30 UTC 
Created attachment 908370 [details]
File: var_log_messages
Comment 11 Milan Crha 2014-06-16 08:35:02 UTC 
(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?
Comment 12 Jamie Lennox 2014-09-02 00:15:16 UTC 
Sorry, I don't know what the exact message was and trying the steps again on a different message seems to work as expected.
Comment 13 Milan Crha 2014-09-02 07:50:22 UTC 
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.