Bug 1397505

Summary: [abrt] evolution: magazine_chain_pop_head(): evolution killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Dawid Zamirski <dzrudy>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: contato.viniciusmorgado, entrox.898, jamescdericco, lilicenco.work, llanbe_t3mp, lucilanga, mbarnes, mcrha, tcfxfzoi, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/696a6d58f050f94a0587dba4f8872ad3928c305a
Whiteboard: abrt_hash:7adfd265ae56226ddbca7f785fa8ece813eaad76;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:26:45 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: exploitable
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 Dawid Zamirski 2016-11-22 16:29:55 UTC
Version-Release number of selected component:
evolution-3.22.1-2.fc25

Additional info:
reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        evolution
crash_function: magazine_chain_pop_head
executable:     /usr/bin/evolution
global_pid:     2924
kernel:         4.8.7-300.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 magazine_chain_pop_head at gslice.c:539
 #1 thread_memory_magazine1_alloc at gslice.c:842
 #2 g_slice_alloc at gslice.c:1016
 #3 g_slice_alloc0 at gslice.c:1051
 #4 g_source_new at gmain.c:916
 #5 g_timeout_source_new_seconds at gmain.c:4734
 #6 g_timeout_add_seconds_full at gmain.c:4919
 #7 camel_sqlite3_file_xSync at camel-db.c:325
 #8 sqlite3PagerCommitPhaseOne at sqlite3.c:52610
 #9 sqlite3BtreeCommitPhaseOne at sqlite3.c:61880

Potential duplicate: bug 979186

Comment 1 Dawid Zamirski 2016-11-22 16:30:01 UTC
Created attachment 1222768 [details]
File: backtrace

Comment 2 Dawid Zamirski 2016-11-22 16:30:02 UTC
Created attachment 1222769 [details]
File: cgroup

Comment 3 Dawid Zamirski 2016-11-22 16:30:03 UTC
Created attachment 1222770 [details]
File: core_backtrace

Comment 4 Dawid Zamirski 2016-11-22 16:30:04 UTC
Created attachment 1222771 [details]
File: dso_list

Comment 5 Dawid Zamirski 2016-11-22 16:30:05 UTC
Created attachment 1222772 [details]
File: environ

Comment 6 Dawid Zamirski 2016-11-22 16:30:06 UTC
Created attachment 1222773 [details]
File: exploitable

Comment 7 Dawid Zamirski 2016-11-22 16:30:08 UTC
Created attachment 1222774 [details]
File: limits

Comment 8 Dawid Zamirski 2016-11-22 16:30:10 UTC
Created attachment 1222775 [details]
File: maps

Comment 9 Dawid Zamirski 2016-11-22 16:30:11 UTC
Created attachment 1222776 [details]
File: mountinfo

Comment 10 Dawid Zamirski 2016-11-22 16:30:12 UTC
Created attachment 1222777 [details]
File: namespaces

Comment 11 Dawid Zamirski 2016-11-22 16:30:13 UTC
Created attachment 1222778 [details]
File: open_fds

Comment 12 Dawid Zamirski 2016-11-22 16:30:14 UTC
Created attachment 1222779 [details]
File: proc_pid_status

Comment 13 Dawid Zamirski 2016-11-22 16:30:15 UTC
Created attachment 1222780 [details]
File: var_log_messages

Comment 14 Milan Crha 2016-11-23 14:11:06 UTC
Thanks for a bug report. I do not recall seeing any similar crash in the recent past, though the backtrace suggests that this was caused by some kind of memory corruption, most likely some code accessing already freed memory and writing to it. Such issues is pretty hard to reproduce, usually. They also usually strike in various places, not in exactly one.

By any chance, do you recall what preceded to this crash, please?

Comment 15 Dawid Zamirski 2016-11-23 16:22:47 UTC
Unfortunately, I do not have any steps to reproduce as ABRT reported this crash when Evolution was not even running at this time. I had this crash happen before on Fedora 25 when it was running but also in that case I also did not do anything specific that I could reproduce. I'll pay close attention going forward in hope to be able to trigger this more reliably on my system.

Comment 16 James C. De Ricco 2017-01-06 20:30:35 UTC
Similar problem has been detected:

evolution-alarm-notify crashed on startup right after logging in.

reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/libexec/evolution/evolution-alarm-notify
crash_function: magazine_chain_pop_head
executable:     /usr/libexec/evolution/evolution-alarm-notify
global_pid:     2012
kernel:         4.8.15-300.fc25.x86_64
package:        evolution-3.22.3-1.fc25
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
reason:         evolution-alarm-notify killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 17 Fedora End Of Life 2017-11-16 14:18:42 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 18 Fedora End Of Life 2017-12-12 10:26:45 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.