| Summary: | [abrt] evolution-data-server: magazine_chain_pop_head(): evolution-calendar-factory-subprocess killed by SIGSEGV | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andrew Cook <ariscop> | ||||||||||||||||||||||||||||
| Component: | evolution-data-server | Assignee: | Milan Crha <mcrha> | ||||||||||||||||||||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||||||
| Version: | 24 | CC: | ariscop, danloomis47, jbirch, jfrieben, jrimpo, mbarnes, mcrha, mustafamahmood1991, normrossiter, r, waterforce1205 | ||||||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/79db823a004746d8d0c02a51a06e3117238cc80b | ||||||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:7bc92b5897237abcfdd4dad53c58ac51d18b34df;VARIANT_ID=workstation; | ||||||||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||||||
| Last Closed: | 2017-08-08 14:01: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
Andrew Cook
2016-03-22 09:37:06 UTC
Created attachment 1138953 [details]
File: backtrace
Created attachment 1138954 [details]
File: cgroup
Created attachment 1138955 [details]
File: core_backtrace
Created attachment 1138956 [details]
File: dso_list
Created attachment 1138957 [details]
File: environ
Created attachment 1138958 [details]
File: exploitable
Created attachment 1138959 [details]
File: limits
Created attachment 1138960 [details]
File: maps
Created attachment 1138961 [details]
File: mountinfo
Created attachment 1138962 [details]
File: namespaces
Created attachment 1138963 [details]
File: open_fds
Created attachment 1138964 [details]
File: proc_pid_status
Created attachment 1138965 [details]
File: var_log_messages
Thanks for a bug report. I see this crashed in a Birthdays & Anniversaries calendar, but I do not see a cause from the backtrace. By any chance, do you know how to reproduce the crash, please? Not a clue; I do keep seeing errors for the "Birthdays & Anniversaries" calendar, but the crash itself is random. Network failure maybe? There's a lot of bugs open for magazine_chain_pop_head, gslice bug? will try with gslice set to always malloc if i find a way to reproduce it It looks, according to the backtrace, like one of the address books was just opened. I cannot tell from the backtrace whether it was due to network disconnect/reconnect. This is not a GSlice bug, it's only a place where the crash was spot. I guess it's due to some memory corruption, like some part of the code writes to a memory which it shouldn't access, effectively overwriting data which doesn't belong to it. Once the overwritten memory is accessed (which can happen anytime later after the faulty write) the issue is recognized. Another option is a use-after-free, where one part of the code frees something and another part tries to read the already freed bits. The valgrind sometimes helps to detect such memory issues, but as it makes the application significantly slower, then it's common that the error doesn't trigger, because of a different thread interleaving or similar change of the execution path caused by the memory checking (slowness). I Guarantee it's GSlice; search for bug reports containing "magazine_chain_pop_head" https://goo.gl/lZrGTr (excludes duplicates) None of these have been fixed, One of them even has someone making the same argument you are, that it must be memory corruption; It's happened in too many places too unreliably to be memory corruption *** Bug 1336471 has been marked as a duplicate of this bug. *** Similar problem has been detected: ABRT reported at system boot. reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory-subprocess --factory contacts --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2159x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/2159/2 crash_function: magazine_chain_pop_head executable: /usr/libexec/evolution-calendar-factory-subprocess global_pid: 2205 kernel: 4.5.5-300.fc24.x86_64 package: evolution-data-server-3.20.2-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: evolution-calendar-factory-subprocess killed by SIGSEGV reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000 *** Bug 1357230 has been marked as a duplicate of this bug. *** *** Bug 1355815 has been marked as a duplicate of this bug. *** *** Bug 1373028 has been marked as a duplicate of this bug. *** This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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. |