Version-Release number of selected component: evolution-3.6.4-3.fc18 Additional info: backtrace_rating: 4 cmdline: evolution crash_function: magazine_chain_pop_head executable: /usr/bin/evolution kernel: 3.8.8-202.fc18.x86_64 uid: 1000 ureports_counter: 1 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:532 #1 magazine_cache_trim at gslice.c:671 #2 magazine_cache_push_magazine at gslice.c:703 #3 thread_memory_magazine2_unload at gslice.c:802 #4 g_slice_free1 at gslice.c:1093 #5 g_list_foreach at glist.c:942 #6 g_list_free_full at glist.c:183 #7 free_node at gtkuimanager.c:1400 #8 g_node_traverse_post_order at gnode.c:620 #11 g_node_traverse at gnode.c:874
Created attachment 738910 [details] File: backtrace
Created attachment 738911 [details] File: cgroup
Created attachment 738912 [details] File: core_backtrace
Created attachment 738913 [details] File: dso_list
Created attachment 738914 [details] File: environ
Created attachment 738915 [details] File: limits
Created attachment 738916 [details] File: maps
Created attachment 738917 [details] File: open_fds
Created attachment 738918 [details] File: proc_pid_status
Created attachment 738919 [details] File: var_log_messages
Created attachment 738920 [details] File: xsession_errors
Thanks for a bug report. Do you have any steps how to reproduce this memory corruption bug, please? The only thing I see from the backtrace is that you use evolution-ews, your EWS account is connecting to the server, and the crash happened on a New Mail Composer close, probably after successful send of a message.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.