trackerd crashed with SIGSEGV in g_slice_alloc()

Bug #147430 reported by John Shaffer
32
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: tracker

There were no actions on my part to trigger this (as far as I am aware).

ProblemType: Crash
Architecture: i386
Date: Sun Sep 30 17:04:37 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/trackerd
NonfreeKernelModules: video nvidia
Package: tracker 0.6.3-0ubuntu1
PackageArchitecture: i386
ProcCmdline: trackerd
ProcCwd: /home/john
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: tracker
StacktraceTop:
 g_slice_alloc () from /usr/lib/libglib-2.0.so.0
 g_array_sized_new () from /usr/lib/libglib-2.0.so.0
 g_byte_array_sized_new () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: trackerd crashed with SIGSEGV in g_slice_alloc()
Uname: Linux 2112 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin mythtv netdev plugdev powerdev scanner tape video

Tags: apport-crash
Revision history for this message
John Shaffer (jshaffer) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_array_sized_new (zero_terminated=0, clear=0, elt_size=1, reserved_size=16) at /build/buildd/glib2.0-2.14.1/glib/garray.c:86
IA__g_byte_array_sized_new (reserved_size=16) at /build/buildd/glib2.0-2.14.1/glib/garray.c:640
update_word_table (table=0x8105100, word=0xb61b6670 "0500cdt", word_details=0xb7a5510c) at tracker-cache.c:248
tracker_cache_add (word=0xb61b6670 "0500cdt", service_id=164228, service_type=18, score=14, is_new=1) at tracker-cache.c:280
append_index_data (key=0xb61b6670, value=0xe, user_data=0x8102970) at tracker-db-sqlite.c:5670

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in tracker:
importance: Undecided → Medium
Revision history for this message
Jamie McCracken (jamiemcc-blueyonder) wrote :

are you able to reliably replicate this crash?

if so does it crash on same word "0500cdt"?

normally a crash (in g_array_sized_new) there is an out of memory thing - can you try and replicate and keep an eye on free ram pls and get back to me

Changed in tracker:
status: New → Incomplete
Revision history for this message
John Shaffer (jshaffer) wrote :

I can't reproduce it at all.

It's extremely unlikely that there wasn't any free memory when it crashed. I couldn't even use up the 1.5GB of RAM, much less the 2GB of swap, when I tried to.

Revision history for this message
Jamie McCracken (jamiemcc-blueyonder) wrote :

closing this bug then - if you can replicate it again then pls reopen

Changed in tracker:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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