Version-Release number of selected component: evolution-3.6.2-3.fc18 Additional info: backtrace_rating: 4 cmdline: evolution crash_function: g_malloc0 executable: /usr/bin/evolution kernel: 3.6.7-5.fc18.x86_64 remote_result: 737451 uid: 1000 xsession_errors: Truncated backtrace: Thread no. 1 (9 frames) #3 g_malloc0 at gmem.c:189 #4 thread_memory_from_self at gslice.c:512 #6 g_slice_free1 at gslice.c:1087 #7 g_list_free_1 at glist.c:166 #8 g_queue_pop_tail at gqueue.c:632 #9 g_async_queue_pop_intern_unlocked at gasyncqueue.c:431 #10 g_async_queue_timeout_pop_unlocked at gasyncqueue.c:572 #11 g_thread_pool_wait_for_new_task at gthreadpool.c:264 #13 g_thread_proxy at gthread.c:797 Potential duplicate: bug 839725
Created attachment 655122 [details] File: backtrace
Created attachment 655123 [details] File: build_ids
Created attachment 655124 [details] File: cgroup
Created attachment 655125 [details] File: core_backtrace
Created attachment 655126 [details] File: dso_list
Created attachment 655127 [details] File: environ
Created attachment 655128 [details] File: limits
Created attachment 655129 [details] File: maps
Created attachment 655130 [details] File: open_fds
Created attachment 655131 [details] File: proc_pid_status
Created attachment 655132 [details] File: smolt_data
Created attachment 655133 [details] File: var_log_messages
Thanks for a bug report. The backtrace shows that the crash happened while allocating a memory, which suggest a memory corruption issues. Do you recall what you did in time of the crash, please? Or, even better, can you reproduce this after certain set of steps, please? Thanks in advance. I see from the backtrace that your MAPI account was about to refresh itself, but nothing more than that, as other threads were also doing something.
When it happens again, I will report the steps. I can't remember what exactly happened... And maybe it will not happen again and it was some temp issue.
attempted to do send/receive after i configure evolution to delete mail box items after 40 days. Then it started crashing. reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /bin/evolution crash_function: g_malloc0 executable: /usr/bin/evolution kernel: 3.9.4-200.fc18.x86_64 package: evolution-3.6.4-3.fc18 reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) runlevel: N 3 uid: 1000 xsession_errors: (evolution-alarm-notify:1193): GConf-WARNING **: Got Disconnected from DBus.
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.