tracker-extract crashed with SIGSEGV in dbus_connection_dispatch()

[Rubén Parra]

Binary package hint: tracker

tracker-extract crashed with SIGSEGV in dbus_connection_dispatch()

ProblemType: Crash
Architecture: amd64
Disassembly: 0x21:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/tracker/tracker-extract
Package: tracker 0.6.91-1ubuntu1
ProcCmdline: /usr/lib/tracker/tracker-extract
ProcEnviron:
 SHELL=/bin/bash
 LANG=es_ES.UTF-8
Signal: 11
SourcePackage: tracker
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libhal.so.1
 dbus_connection_dispatch () from /lib/libdbus-1.so.3
 ?? () from /usr/lib/libdbus-glib-1.so.2
 g_main_context_dispatch ()
Title: tracker-extract crashed with SIGSEGV in dbus_connection_dispatch()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()
filter_func (connection=<value optimized out>,
dbus_connection_dispatch (connection=0x1306690)
message_queue_dispatch (
IA__g_main_context_dispatch (context=0x108ab70)

[Martyn Russell (martyn-lanedo)]

The crash here doesn't look like it is in Tracker. The data here doesn't help identify the problem area either :(

[capacman (achalil)]

It said it is in tracker-extract. Yesterday i upgraded from 8.10 to 9.04 and
tracker reindexed everything. It gave me this error two time but now
indexing already finished. If you want i can delete all index and make it
reindex again to produce error. Is there any startup arguments for tracker
to give us more info about this crash? I will start it in this way if
possible

2009/3/30 Martyn Russell <email address hidden>

> The crash here doesn't look like it is in Tracker. The data here doesn't
> help identify the problem area either :(
>
> --
> tracker-extract crashed with SIGSEGV in dbus_connection_dispatch()
> https://bugs.launchpad.net/bugs/346413
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Martyn Russell (martyn-lanedo)]

This should be fixed by now. I think there is a patch which plays with setrlimit. I think a lot of crashes in the extractor are due to this - currently we set memory limits of 128Mb (512Mb for AMD64 processors) for tracker-extract processes and we seem to be getting SIGSEGV because of that It think. This is at least one possible reason.

NOTE: tracker-extract is allowed to crash, it is a separate process because some extensions we use to get metadata are buggy and we can not guarantee stability when integrating with so many different libraries to get file metadata. As such we expect a lot of crashes with tracker-extract. We are of course trying to tidy those all up as much as possible. So if you can reindex and get it to crash again, great. Set the verbosity to 3 in $HOME/.config/tracker.cfg and then see which file causes it in $HOME/.local/share/tracker/tracker-extract.log so we can play with that file and figure it out.