Bug 1298088

Summary: [abrt] evolution: camel_flag_list_copy(): evolution killed by SIGABRT
Product: [Fedora] Fedora Reporter: Heiko Adams <bugzilla>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: lucilanga, mbarnes, mcrha, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/86c3959ed9e9d09423f799b57e1f38c47072ae69
Whiteboard: abrt_hash:7f05733c61e3b16d63d7d789da65476958f2879b;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 17:50:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Heiko Adams 2016-01-13 08:41:21 UTC 
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
Comment 1 Heiko Adams 2016-01-13 08:41:29 UTC 
Created attachment 1114325 [details]
File: backtrace
Comment 2 Heiko Adams 2016-01-13 08:41:31 UTC 
Created attachment 1114326 [details]
File: cgroup
Comment 3 Heiko Adams 2016-01-13 08:41:34 UTC 
Created attachment 1114327 [details]
File: core_backtrace
Comment 4 Heiko Adams 2016-01-13 08:41:36 UTC 
Created attachment 1114328 [details]
File: dso_list
Comment 5 Heiko Adams 2016-01-13 08:41:37 UTC 
Created attachment 1114329 [details]
File: environ
Comment 6 Heiko Adams 2016-01-13 08:41:38 UTC 
Created attachment 1114330 [details]
File: limits
Comment 7 Heiko Adams 2016-01-13 08:41:42 UTC 
Created attachment 1114331 [details]
File: maps
Comment 8 Heiko Adams 2016-01-13 08:41:43 UTC 
Created attachment 1114332 [details]
File: mountinfo
Comment 9 Heiko Adams 2016-01-13 08:41:45 UTC 
Created attachment 1114333 [details]
File: namespaces
Comment 10 Heiko Adams 2016-01-13 08:41:46 UTC 
Created attachment 1114334 [details]
File: open_fds
Comment 11 Heiko Adams 2016-01-13 08:41:48 UTC 
Created attachment 1114335 [details]
File: proc_pid_status
Comment 12 Heiko Adams 2016-01-13 08:41:49 UTC 
Created attachment 1114336 [details]
File: var_log_messages
Comment 13 Milan Crha 2016-01-19 16:17:25 UTC 
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.
Comment 14 Milan Crha 2016-01-19 16:20:21 UTC 
Just for a reference, the possible issue is reported upstream as:
https://bugzilla.gnome.org/show_bug.cgi?id=680471
Comment 15 Fedora End Of Life 2016-11-24 14:53:38 UTC 
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.
Comment 16 Fedora End Of Life 2016-12-20 17:50:09 UTC 
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.