tracker-store crashed with SIGSEGV in g_slice_alloc()

Bug #984491 reported by Rik Goldman
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
New
Undecided
Unassigned

Bug Description

i have no idea. unity keeps crashing, don't know if this bug is related

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: tracker 0.14.0-2ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
Date: Tue Apr 17 18:59:57 2012
ExecutablePath: /usr/lib/tracker/tracker-store
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/lib/tracker/tracker-store
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f14a7df7dfa <g_slice_alloc+490>: mov (%rbx),%rdx
 PC (0x7f14a7df7dfa) ok
 source "(%rbx)" (0x00000002) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: tracker-store crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to precise on 2012-03-23 (25 days ago)
UserGroups: www-data

Revision history for this message
Rik Goldman (rikgoldman) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #964411, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
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.