*** This bug is a duplicate of bug 346388 ***
https://bugs.launchpad.net/bugs/346388
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.
--
tracker-extract crashed with SIGSEGV in dbus_connection_dispatch()
https://bugs.launchpad.net/bugs/346413
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
