Bug 589602
| Summary: | [abrt] crash in tracker-0.8.4-1.fc13: magazine_chain_pop_head: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Javier Alejandro Castro <javier.alejandro.castro> | ||||||
| Component: | tracker | Assignee: | Deji Akingunola <dakingun> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 13 | CC: | alfredo.pons, bloch, dakingun, stefano.sintoni.cnigroup | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | abrt_hash:9d664742fb55284ccc0dbee8173a4ed0a5aa0b5b | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-06-27 16:08:35 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Javier Alejandro Castro
2010-05-06 14:26:34 UTC
Created attachment 412071 [details]
File: backtrace
According to a upstream developer; 'At first glance it either looks to me like a memory corruption, or a GIO bug. On the crashing thread there is nothing but GIO functions, and I find it quite suspicious that it crashes on allocating memory (Usually a symptom of memory corruption)'. Can you run tracker-miner-fs under valgrind? $ G_SLICE=always_malloc valgrind --leak-check=full --num-callers=30 --log-file=valgrind.log ./tracker-miner-fs -v 3 and report back with the valgrind.log file? This error never happened again. Anyway, do you want me to do that thing, even when tracker does not crash anymore? Cause i dont see it is a always reproducible error. (In reply to comment #3) > This error never happened again. Anyway, do you want me to do that thing, even > when tracker does not crash anymore? Yes, please do. > Cause i dont see it is a always reproducible error. Created attachment 413791 [details]
The requested valgrind log file
Here is the requested valgrind log file. I've run the miner-fs, when it finished i did Ctrl+C. Hope this helps!
*** Bug 605691 has been marked as a duplicate of this bug. *** *** Bug 648802 has been marked as a duplicate of this bug. *** *** Bug 573232 has been marked as a duplicate of this bug. *** *** Bug 636897 has been marked as a duplicate of this bug. *** This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 WONTFIX if it remains open with a Fedora 'version' of '13'. 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 prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. Thank you for reporting this bug and we are sorry it could not be fixed. |