Re: [Tracker] ubuntu-gnome/+bug/1653392



Hi,

On Wed, Feb 22, 2017 at 6:54 PM, Chris <cpollock embarqmail com> wrote:
On Wed, 2017-02-22 at 11:09 +0100, Carlos Garnacho wrote:
Hi Chris,

On Wed, Feb 22, 2017 at 12:30 AM, Chris <cpollock embarqmail com>
wrote:

I'm sure hoping I'm sending this to the correct list. If not I

It is :)


sincerely apologize. I've been experiencing this - tracker-store
crashed with SIGSEGV in g_slice_alloc()  almost daily since
12/31/2016.
It's listed here - https://bugs.launchpad.net/ubuntu-gnome/+bug/165
3392
 still shown as new and assigned to nobody. Here is some version
information:

Strange, that link doesn't work here, just says "page not found".
Anyway, SIGSEGV when allocating memory is a pretty good indicator of
memory corruption. Valgrind could be of help there, you can run
tracker-store through valgrind with:

killall -15 tracker-store; valgrind --leak-check=full --num-
callers=25
--log-file=~/not-indexed-folder/tracker-store-valgrind.txt
/usr/lib/tracker/tracker-store

This will make tracker-store real slow (and all re-indexing process
in
chain effect), but it should catch and log invalid frees/writes into
that log file.

Oh, also make sure you have debug packages for tracker, I forgot what
the ubuntu way is for that.



Distributor ID: Ubuntu
Description:    Ubuntu 16.04.2 LTS
Release:        16.04
Codename:       xenial

chris@localhost:~$ apt-cache policy tracker
tracker:
  Installed: 1.8.3-0ubuntu0~xenial1
  Candidate: 1.8.3-0ubuntu0~xenial1
  Version table:
 *** 1.8.3-0ubuntu0~xenial1 500
        500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubu
ntu
xenial/main amd64 Packages

Hmm, however, 1.8.x is slightly old now, you should perhaps try first
with the 1.10.x stable branch which has been out for a few months
now.
Although I tbh don't remember recent tracker-store memory corruption
bugs, nor having seen anything like that fixed recently.

If after updating the bug still persists, please file a bug at
https://bugzilla.gnome.org/enter_bug.cgi?product=tracker with the
valgrind info and we'll take it from there.

Cheers,
  Carlos

Carlos, an update to tracker 1.8.3-0ubuntu0~xenial2 was put out a bit
ago, I installed

tracker-gui amd64 1.8.3-0ubuntu0~xenial2
tracker-miner-fs amd64 1.8.3-0ubuntu0~xenial2
gir1.2-tracker-1.0 amd64 1.8.3-0ubuntu0~xenial2
tracker-extract amd64 1.8.3-0ubuntu0~xenial2
libtracker-miner-1.0-0 amd64 1.8.3-0ubuntu0~xenial2
tracker amd64 1.8.3-0ubuntu0~xenial2
libtracker-control-1.0-0 amd64 1.8.3-0ubuntu0~xenial2
libtracker-sparql-1.0-0 amd64 1.8.3-0ubuntu0~xenial2

They all came from - http://ppa.launchpad.net/gnome3-team/gnome3-stagin
g/ubuntu xenial/main amd64

Since the bug has a habit of popping up daily I'll see what happens

Thanks! I provided the fix in that package after I was granted access
to the bug you filed and saw the logs. It is also in tracker git now
fwiw.

I'm however surprised that you get through these error paths, please
keep an eye on "Transaction rollback failed" warnings from
tracker-store, as I wouldn't really expect these to happen, it
shouldn't crash anymore though.

Cheers,
  Carlos


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]