Re: [Tracker] tracker-miner-fs crash?

[Martyn Russell <martyn lanedo com>]

On 04/11/09 15:37, Tshepang Lekhonkhobe wrote:
> I'm now getting this crash:
>
> (tracker-miner-fs:6170): Tracker-DEBUG: No more events to pair, removing timeout
>
> (tracker-miner-fs:6170): Tracker-CRITICAL **: Could not execute
> sparql: Did not receive a reply. Possible causes include: the remote
> application did not send a reply, the message bus security policy
> blocked the reply, the reply timeout expired, or the network
> connection was broken.
>
> (tracker-miner-fs:6170): Tracker-CRITICAL **: Could not execute
> sparql: Did not receive a reply. Possible causes include: the remote
> application did not send a reply, the message bus security policy
> blocked the reply, the reply timeout expired, or the network
> connection was broken.
>
> (tracker-miner-fs:6170): Tracker-CRITICAL **: Could not execute
> sparql: Did not receive a reply. Possible causes include: the remote
> application did not send a reply, the message bus security policy
> blocked the reply, the reply timeout expired, or the network
> connection was broken.
>
> (tracker-miner-fs:6170): Tracker-CRITICAL **: Could not execute
> sparql: Did not receive a reply. Possible causes include: the remote
> application did not send a reply, the message bus security policy
> blocked the reply, the reply timeout expired, or the network
> connection was broken.

These criticals are due to the tracker-store crash which Philip fixed.

> Program received signal SIGSEGV, Segmentation fault.
> 0xb7e4edbe in item_update_uri_recursively_cb (miner=0x807d810,
> result=0xb7e20ff4, error=0x82dcbc0, user_data=0xbfffeb30) at
> tracker-miner-fs.c:1025
> 1025                            child_source_uri = g_ptr_array_index (result, i);
> (gdb) bt
> #0  0xb7e4edbe in item_update_uri_recursively_cb (miner=0x807d810,
> result=0xb7e20ff4, error=0x82dcbc0, user_data=0xbfffeb30) at
> tracker-miner-fs.c:1025
> #1  0xb7e4b5d0 in run_query_callback (result=0xb7e20ff4,
> error=0x82dcbc0, user_data=0x8084e20) at tracker-miner.c:778
> #2  sparql_query_cb (result=0xb7e20ff4, error=0x82dcbc0,
> user_data=0x8084e20) at tracker-miner.c:804

I checked this code and it looks sane to me. Perhaps we need to re-run 
this in valgrind to see what happens.

> > On lun, 2009-11-02 at 18:30 +0200, Tshepang Lekhonkhobe wrote:
> > > On Mon, Nov 2, 2009 at 17:34, Carlos Garnacho<carlosg gnome org>  wrote:
> > > > I've just fixed it in master HEAD, thanks for the heads up!
> > >
> > > Still occurs :-(
> > >
> > > > On lun, 2009-11-02 at 16:44 +0200, Tshepang Lekhonkhobe wrote:
> > > > > Hi,
> > > > >
> > > > > Am not sure if this is a Debian-only problem:
> > > > >
> > > > > <START>
> > > > > Tracker-Message: Crawling recursively directory '/usr/share/applications'
> > > > >
> > > > > (tracker-miner-fs:9489): Tracker-CRITICAL **: Could not obtain the
> > > > > mounted volumes

This warning is about tracker-store crashing which Philip fixed. I was 
seeing this too.

> > > > > Program received signal SIGSEGV, Segmentation fault.
> > > > > 0xb7c00f99 in IA__g_ptr_array_foreach (array=0xb7e20ff4,
> > > > > func=0xb7c4acc0<IA__g_strfreev>, user_data=0x0)
> > > > >      at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/garray.c:818
> > > > > 818   /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/garray.c:
> > > > > No such file or directory.
> > > > >        in /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/garray.c
> > > > > (gdb) bt
> > > > > #0  0xb7c00f99 in IA__g_ptr_array_foreach (array=0xb7e20ff4,
> > > > > func=0xb7c4acc0<IA__g_strfreev>, user_data=0x0)
> > > > >      at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/garray.c:818
> > > > > #1  0xb7f66f2e in tracker_dbus_results_ptr_array_free
> > > > > (ptr_array=0xbfffecb0) at tracker-dbus.c:240
> > > > > #2  0xb7e4b59f in sparql_query_cb (result=0xb7e20ff4, error=0x807bb90,
> > > > > user_data=0x8084b60) at tracker-miner.c:797
> > > > > #3  0xb7e71045 in tracker_GPtrArray_reply (proxy=0x806b278,
> > > > > OUT_result=0xb7e20ff4, error=0x807bb90, user_data=0x80851d8) at
> > > > > tracker.c:78

Are you still getting these errors since the tracker-store bug was fixed?


--
Regards,
Martyn