|Summary:||[abrt] crash in tracker-0.8.11-1.fc13: magazine_chain_pop_head: Process /usr/libexec/tracker-extract was killed by signal 11 (SIGSEGV)|
|Product:||[Fedora] Fedora||Reporter:||Tomasz Torcz <tomek>|
|Component:||gstreamer||Assignee:||Benjamin Otte <otte>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||13||CC:||dakingun, dwmw2, otte|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2011-06-27 18:43:34 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Tomasz Torcz 2010-06-22 07:10:17 UTC
abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/tracker-extract component: tracker crash_function: magazine_chain_pop_head executable: /usr/libexec/tracker-extract global_uuid: 2d25928bc84d829b0bced81671f6a863ad0169ae kernel: 22.214.171.124-124.fc13.x86_64 package: tracker-0.8.11-1.fc13 rating: 4 reason: Process /usr/libexec/tracker-extract was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) How to reproduce: 1. Happened out of blue.
Comment 2 Deji Akingunola 2010-06-22 13:47:02 UTC
This look like some memory corruption in gstreamer, re-assigning.
Comment 3 Benjamin Otte 2010-06-22 14:41:12 UTC
Could you upload the file it was trying to index, so we can be sure? According to the backtrace, that file is /media/WDP-Crypt/Backup/Documents and Settings/113008943/Local Settings/Temporary Internet Files/Content.IE5/4PK74V4N/smallposition.gif
Comment 4 Tomasz Torcz 2010-06-22 15:02:01 UTC
Created attachment 425966 [details] smallposition.gif
Comment 5 Benjamin Otte 2010-06-22 18:00:30 UTC
That file works fine in GStreamer. So I'm tempted to agree that it is a memory corruption, but think the memory corruption happened in tracker-extract when it was processing a previous file and only became visible when GStreamer played with it. Unless someone finds the problem by running tracker-extract under valgrind, there's not a lot I can do about it.
Comment 6 Bug Zapper 2011-06-01 15:56:57 UTC
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
Comment 7 Bug Zapper 2011-06-27 18:43:34 UTC
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.