tracker-store crashed with SIGSEGV in tracker_db_statement_execute()

Bug #1244959 reported by Jens Kehne
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Appears to happen whenever I use tracker in any way. Interestingly, searching in tracker still works normally.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: tracker 0.16.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
CrashCounter: 1
Date: Sat Oct 26 15:16:10 2013
ExecutablePath: /usr/lib/tracker/tracker-store
InstallationDate: Installed on 2012-06-05 (507 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: /usr/lib/tracker/tracker-store
ProcEnviron:
 SHELL=/usr/bin/fish
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7febbca404b0 <tracker_db_statement_execute>: mov 0x28(%rdi),%ecx
 PC (0x7febbca404b0) ok
 source "0x28(%rdi)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
 tracker_db_statement_execute () from /usr/lib/tracker-0.16/libtracker-data.so.0
 tracker_db_interface_sqlite_fts_update_text () from /usr/lib/tracker-0.16/libtracker-data.so.0
 ?? () from /usr/lib/tracker-0.16/libtracker-data.so.0
 tracker_data_update_buffer_flush () from /usr/lib/tracker-0.16/libtracker-data.so.0
 ?? () from /usr/lib/tracker-0.16/libtracker-data.so.0
Title: tracker-store crashed with SIGSEGV in tracker_db_statement_execute()
UpgradeStatus: Upgraded to saucy on 2013-10-26 (0 days ago)
UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare src sudo tracing vboxusers wireshark

Revision history for this message
Jens Kehne (jkehne) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 tracker_db_statement_execute (stmt=0x0, error=0x7febb2ffc8d8) at tracker-db-interface-sqlite.c:2212
 tracker_db_interface_sqlite_fts_update_text (db_interface=db_interface@entry=0x168a8d0, id=100498, properties=<optimized out>, text=<optimized out>, create=create@entry=0) at tracker-db-interface-sqlite.c:1100
 tracker_data_resource_buffer_flush (error=error@entry=0x7febb2ffca08) at tracker-data-update.c:993
 tracker_data_update_buffer_flush (error=error@entry=0x7febb2ffcb18) at tracker-data-update.c:1038
 tracker_sparql_query_execute_insert_or_delete (self=self@entry=0x1705700, update_blank_nodes=update_blank_nodes@entry=0x0, error=error@entry=0x7febb2ffcc78) at /home/martyn/Source/tracker/src/libtracker-data/tracker-sparql-query.vala:759

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in tracker (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Jens Kehne (jkehne)
description: updated
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in tracker (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.