Version-Release number of selected component: evolution-3.10.4-2.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/evolution crash_function: g_malloc0 executable: /usr/bin/evolution kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 21446 Truncated backtrace: Thread no. 1 (10 frames) #2 g_malloc0 at gmem.c:134 #3 g_malloc0_n at gmem.c:369 #4 g_hash_table_new_full at ghash.c:667 #5 g_hash_table_new at ghash.c:623 #6 camel_mime_message_init at camel-mime-message.c:379 #7 g_type_create_instance at gtype.c:1868 #8 g_object_new_internal at gobject.c:1746 #11 camel_mime_message_new at camel-mime-message.c:408 #12 imapx_get_message_sync at camel-imapx-folder.c:563 #13 camel_folder_get_message_sync at camel-folder.c:3838 Potential duplicate: bug 879098
Created attachment 875546 [details] File: backtrace
Created attachment 875547 [details] File: cgroup
Created attachment 875548 [details] File: core_backtrace
Created attachment 875549 [details] File: dso_list
Created attachment 875550 [details] File: environ
Created attachment 875551 [details] File: exploitable
Created attachment 875552 [details] File: limits
Created attachment 875553 [details] File: maps
Created attachment 875554 [details] File: open_fds
Created attachment 875555 [details] File: proc_pid_status
Created attachment 875556 [details] File: var_log_messages
Thanks for a bug report. The only thing I can see in the crashing thread is that it crashed when allocation memory of 32 bytes. As this might not be an issue with a memory space, I suppose it is cause by some memory corruption, like if some code writes to an already freed memory or similar. Such issues can strike anytime, not necessarily immediately when they happen. Due to this, I do not expect you have any steps for a crash reproducer, do you?
no reproducer
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.