Hide Forgot
Description of problem: Just cleaned the trash-folders before evolution crashed Version-Release number of selected component: evolution-3.18.3-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: evolution crash_function: camel_flag_list_copy executable: /usr/bin/evolution global_pid: 3471 kernel: 4.3.3-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #7 camel_flag_list_copy at camel-folder-summary.c:4209 #8 imapx_update_user_flags at camel-imapx-utils.c:285 #9 imapx_update_message_info_flags at camel-imapx-utils.c:343 #10 imapx_untagged_fetch at camel-imapx-server.c:1200 #11 imapx_untagged at camel-imapx-server.c:1903 #12 imapx_step at camel-imapx-server.c:2314 #13 camel_imapx_server_process_command_sync at camel-imapx-server.c:3725 #14 imapx_server_idle_thread at camel-imapx-server.c:5958 #15 g_thread_proxy at gthread.c:778 Potential duplicate: bug 1181079
Created attachment 1114325 [details] File: backtrace
Created attachment 1114326 [details] File: cgroup
Created attachment 1114327 [details] File: core_backtrace
Created attachment 1114328 [details] File: dso_list
Created attachment 1114329 [details] File: environ
Created attachment 1114330 [details] File: limits
Created attachment 1114331 [details] File: maps
Created attachment 1114332 [details] File: mountinfo
Created attachment 1114333 [details] File: namespaces
Created attachment 1114334 [details] File: open_fds
Created attachment 1114335 [details] File: proc_pid_status
Created attachment 1114336 [details] File: var_log_messages
Thanks for a bug report. I do not know whether this is the case, the crash reason is: > double free or corruption (fasttop) but it's possible that one thread, maybe the UI thread, was accessing members of some message info structure, while this thread was also accessing it, and due to thread interleaving the memory got corrupted (the message info structure isn't thread safe, even multiple threads can change the values of it at the same time). It doesn't happen that often, fortunately. As I said, I do not know for sure whether it's the case or not here.
Just for a reference, the possible issue is reported upstream as: https://bugzilla.gnome.org/show_bug.cgi?id=680471
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.