Re: [Tracker] tracker-miner-fs crash?
- From: Philip Van Hoof <spam pvanhoof be>
- To: Tshepang Lekhonkhobe <tshepang gmail com>
- Cc: Carlos Garnacho <carlosg gnome org>, Tracker mailing list <tracker-list gnome org>
- Subject: Re: [Tracker] tracker-miner-fs crash?
- Date: Tue, 10 Nov 2009 16:18:52 +0100
On Tue, 2009-11-10 at 17:14 +0200, Tshepang Lekhonkhobe wrote:
On Tue, Nov 10, 2009 at 17:08, Tshepang Lekhonkhobe<tshepang gmail com> wrote:
Auwch, this is memory corruption in the gslice magazine allocator.
This new issue isn't related to the corruption btw. But right that you
can't continue with fatal-criticals unless this new issue is fixed.
We'll need to you to run valgrind with
export G_SLICE=always-malloc
export G_DEBUG=gc-friendly
And reproduce to find this issue
You can also set G_DEBUG=fatal-criticals so that we can find where the
criticals are coming from. If we are lucky those criticals are related
to the memory corruption. Meaning that we have good assertions ;-)
running:
$ G_SLICE=always-malloc G_DEBUG=fatal-criticals valgrind
--leak-check=full --show-reachable=yes --leak-resolution=high -v
--log-file=valgrind.log /usr/libexec/tracker-miner-fs
produces a quick crash:
[snip]
Tracker-Message: Starting next miner...
(tracker-miner-fs:23552): Tracker-DEBUG: URN '(null)' (mount point:
Owk, so your device's URN is NULL. That's probably why I'm not seeing
this here.
Can you reproduce this in gdb instead and give me a a copypaste of what
thread apply all bt in gdb tells you?
urn:nepomuk:datasource:9291a450-1d49-11de-8c30-0800200c9a66) was not
reported to be mounted, but now it is, updating state
(tracker-miner-fs:23552): Tracker-DEBUG: Setting up mount point
'urn:nepomuk:datasource:9291a450-1d49-11de-8c30-0800200c9a66'
Tracker-Message: Crawling recursively directory '/usr/share/applications'
Tracker-CRITICAL **: Could not initialize currently active mount
points: 1.345: syntax error, undefined variable
aborting...
Aborted
and now with --track-origins=yes, find attached
That regretfully doesn't help to track this issue.
--
Philip Van Hoof, freelance software developer
home: me at pvanhoof dot be
gnome: pvanhoof at gnome dot org
http://pvanhoof.be/blog
http://codeminded.be
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]