tracker-indexer crashed with SIGSEGV in tracker_db_result_set_get()

Bug #432110 reported by josa
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: tracker

Ubuntu: Karmic
Tracker: 0.6.95-1ubuntu1

I had just logged in after restarting computer when apport reported tracker crash about one minute or so. Tracker was still running and searching seemed to work just fine.

When ubuntu was turning off as I had requested restart I got an at-spi crash that I updated bug 423947 with. Restart was more or less a mistake from my side and not really needed as far as I know.

ProblemType: Crash
Architecture: amd64
CheckboxSubmission: e48fc7f3185d255bb3750ca6084d4ff4
CheckboxSystem: 1520e0fec62b79de6eb677ed5d80c2d6
CrashCounter: 1
Date: Thu Sep 17 21:10:05 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/tracker/tracker-indexer
Package: tracker 0.6.95-1ubuntu1
ProcCmdline: /usr/lib/tracker/tracker-indexer
ProcCwd: /
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
SegvAnalysis:
 Segfault happened at: 0x7fbcaf76b3d5 <tracker_db_result_set_get+565>: mov (%r15,%rdx,8),%rsi
 PC (0x7fbcaf76b3d5) ok
 source "(%r15,%rdx,8)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
 tracker_db_result_set_get (
 db_get_metadata (service=<value optimized out>,
 item_erase (indexer=0x1671030, service=0x15ee000,
 cleanup_task_func (user_data=0x1671030)
 g_timeout_dispatch (source=0x175c050,
Title: tracker-indexer crashed with SIGSEGV in tracker_db_result_set_get()
Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
josa (johnny-sander) wrote :
Revision history for this message
josa (johnny-sander) wrote :

Got two tracker apport reports after about one minute on first log in today. Traces are the same as bug attachments. I think it was when tracker went idle after first index search or what it is it does.
Tracker still running and works fine.

Revision history for this message
josa (johnny-sander) wrote :

Removed CoreDump and made report public. Original file saved in case it is needed.

visibility: private → public
josa (johnny-sander)
tags: removed: need-amd64-retrace
Revision history for this message
josa (johnny-sander) wrote :

Keeps happening every day.
Would it be of any use to have a new report with newer version of apport?

Revision history for this message
Robert Roth (evfool) wrote :

Thank you for reporting this bug to Ubuntu. Karmic reached EOL on April 30, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with Precise and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.

Changed in tracker (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for tracker (Ubuntu) because there has been no activity for 60 days.]

Changed in tracker (Ubuntu):
status: Incomplete → Expired
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.