Hi Ian, It may well be a rogue file being indexed. We've just fixed a bug which was allocating way too much memory here: https://bugzilla.gnome.org/show_bug.cgi?id=748608
This started off as a Tracker bug in tracker-extract too. Turned out to be a library we depend on. The bug also mentions a link which I've added recently to help people investigate these issues, here is the link again: https://wiki.gnome.org/Projects/Tracker/Documentation/Debugging#High_memory_use.3F Are you able to share the output of: $ tracker-extract -v 3 -f /path/to/file ? That might shed some light on this issue. Alternatively, if you could attach the file in question for testing here, that could help too. Thanks :) ** Bug watch added: GNOME Bug Tracker #748608 https://bugzilla.gnome.org/show_bug.cgi?id=748608 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1364780 Title: tracker-extract crashed with SIGABRT in g_malloc0() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1364780/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
