Bug 1079740 - [abrt] tracker: wherePathSatisfiesOrderBy(): tracker-store killed by SIGSEGV
Summary: [abrt] tracker: wherePathSatisfiesOrderBy(): tracker-store killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: tracker
Version: 20
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Igor Gnatenko
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:1acb1029becc1fd1eb668f7a613...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-23 16:06 UTC by Pablo Rodríguez
Modified: 2015-06-29 19:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 19:39:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (59.52 KB, text/plain)
2014-03-23 16:06 UTC, Pablo Rodríguez
no flags Details
File: cgroup (159 bytes, text/plain)
2014-03-23 16:06 UTC, Pablo Rodríguez
no flags Details
File: core_backtrace (21.85 KB, text/plain)
2014-03-23 16:06 UTC, Pablo Rodríguez
no flags Details
File: dso_list (2.79 KB, text/plain)
2014-03-23 16:06 UTC, Pablo Rodríguez
no flags Details
File: environ (1.06 KB, text/plain)
2014-03-23 16:06 UTC, Pablo Rodríguez
no flags Details
File: exploitable (82 bytes, text/plain)
2014-03-23 16:07 UTC, Pablo Rodríguez
no flags Details
File: limits (1.29 KB, text/plain)
2014-03-23 16:07 UTC, Pablo Rodríguez
no flags Details
File: maps (15.36 KB, text/plain)
2014-03-23 16:07 UTC, Pablo Rodríguez
no flags Details
File: open_fds (1.26 KB, text/plain)
2014-03-23 16:07 UTC, Pablo Rodríguez
no flags Details
File: proc_pid_status (800 bytes, text/plain)
2014-03-23 16:07 UTC, Pablo Rodríguez
no flags Details
File: var_log_messages (550 bytes, text/plain)
2014-03-23 16:07 UTC, Pablo Rodríguez
no flags Details

Description Pablo Rodríguez 2014-03-23 16:06:21 UTC
Description of problem:
Affected by #1075889, I applied the solution proposed in its comment #15.

But after having searched on another nautilus window,  I ran into #1031443.

tracker-store leaked 100% CPU for a minute or so. Then it crashed.

This is the bug I’m reporting.

Version-Release number of selected component:
tracker-0.16.4-2.fc20

Additional info:
reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-store
crash_function: wherePathSatisfiesOrderBy
executable:     /usr/libexec/tracker-store
kernel:         3.13.6-200.fc20.i686
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 wherePathSatisfiesOrderBy at sqlite3.c:114178
 #1 wherePathSolver at sqlite3.c:114575
 #2 sqlite3WhereBegin at sqlite3.c:114969
 #3 sqlite3Select at sqlite3.c:104775
 #4 yy_reduce at sqlite3.c:117722
 #5 sqlite3Parser at sqlite3.c:53224
 #6 sqlite3RunParser at sqlite3.c:119590
 #7 sqlite3Prepare at sqlite3.c:99779
 #8 sqlite3LockAndPrepare at sqlite3.c:99871
 #9 tracker_db_interface_create_statement at tracker-db-interface-sqlite.c:1367

Comment 1 Pablo Rodríguez 2014-03-23 16:06:32 UTC
Created attachment 877862 [details]
File: backtrace

Comment 2 Pablo Rodríguez 2014-03-23 16:06:37 UTC
Created attachment 877863 [details]
File: cgroup

Comment 3 Pablo Rodríguez 2014-03-23 16:06:45 UTC
Created attachment 877864 [details]
File: core_backtrace

Comment 4 Pablo Rodríguez 2014-03-23 16:06:49 UTC
Created attachment 877865 [details]
File: dso_list

Comment 5 Pablo Rodríguez 2014-03-23 16:06:58 UTC
Created attachment 877866 [details]
File: environ

Comment 6 Pablo Rodríguez 2014-03-23 16:07:00 UTC
Created attachment 877867 [details]
File: exploitable

Comment 7 Pablo Rodríguez 2014-03-23 16:07:18 UTC
Created attachment 877868 [details]
File: limits

Comment 8 Pablo Rodríguez 2014-03-23 16:07:20 UTC
Created attachment 877869 [details]
File: maps

Comment 9 Pablo Rodríguez 2014-03-23 16:07:27 UTC
Created attachment 877870 [details]
File: open_fds

Comment 10 Pablo Rodríguez 2014-03-23 16:07:33 UTC
Created attachment 877871 [details]
File: proc_pid_status

Comment 11 Pablo Rodríguez 2014-03-23 16:07:42 UTC
Created attachment 877872 [details]
File: var_log_messages

Comment 12 Fedora Admin XMLRPC Client 2014-07-26 17:13:22 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 13 Fedora Admin XMLRPC Client 2014-07-27 06:35:24 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

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

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 20 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 15 Fedora End Of Life 2015-06-29 19:39:33 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.


Note You need to log in before you can comment on or make changes to this bug.