i am getting this immediately after gnome signon 16.10 UBUNTU.
--
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
In answer to @martyn-lanedo: I'm not sure how to reproduce this
reliably, except that it happens for me in *every* ubuntu-gnome session
(15.04) within 15 minutes or so of login. But it seems to be triggered
by a background tracker action, not by an attempt to extract a
particular file directly. If
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
** Tags added: bugpattern-needed
--
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:
** Tags added: vivid
--
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:
Crash occurs sometimes immediately after login. Captured full stack-
trace for a recent occurrence.
** Attachment added: Stack trace for tracker-extract crash
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1364780/+attachment/4210721/+files/tracker-extract-stacktrace.txt
--
You
Hi all,
I am one of the upstream maintainers. I think I've seen this bug recently but
need a way to reliably reproduce it to fix it.
Does anyone have a way to do that?
Normally, if you know the file in question being extracted, you should
be able to run this on the command line to reproduce the
Just to add, my initial suspicion is either:
a) a rogue extractor
b) the kernel could be killing us due to too much memory use, based on our call
to setrlimit() which we mainly only use in tracker-extract. The limit = CLAMP
(total_halfed, MEM_LIMIT_MIN, G_MAXLONG); where MEM_LIMIT_MIN = 256 Mb.
** Information type changed from Private to Public
--
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
