Re: [Tracker] tracker-store crash

[Tshepang Lekhonkhobe <tshepang gmail com>]

Tracker:ERROR:tracker-db-interface-sqlite.c:1231:tracker_db_statement_sqlite_reset:
assertion failed: (!priv->stmt_is_sunk)

Program received signal SIGABRT, Aborted.
0xb7fe1424 in __kernel_vsyscall ()
(gdb) bt
#0  0xb7fe1424 in __kernel_vsyscall ()
#1  0xb7ab53d0 in *__GI_raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2  0xb7ab8a85 in *__GI_abort () at abort.c:88
#3  0xb7c86c2c in IA__g_assertion_message (domain=0xb7fd4f8b
"Tracker", file=0xb7fdaacd "tracker-db-interface-sqlite.c", line=1231,
    func=0xb7fdae40 "tracker_db_statement_sqlite_reset",
message=0x8414010 "assertion failed: (!priv->stmt_is_sunk)")
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gtestutils.c:1302
#4  0xb7c8724d in IA__g_assertion_message_expr (domain=0xb7fd4f8b
"Tracker", file=0xb7fdaacd "tracker-db-interface-sqlite.c", line=1231,
    func=0xb7fdae40 "tracker_db_statement_sqlite_reset",
expr=0xb7fdab0b "!priv->stmt_is_sunk") at
/build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gtestutils.c:1313
#5  0xb7fc555c in tracker_db_statement_sqlite_reset (stmt=<value
optimized out>) at tracker-db-interface-sqlite.c:1231
#6  0xb7fc55ad in tracker_db_interface_sqlite_create_statement
(db_interface=0x806f0f0, query=0x80662b8 "SELECT \"dc:source\" FROM
\"rdfs:Resource_dc:source\" WHERE ID = ?")
    at tracker-db-interface-sqlite.c:506
#7  0xb7fc204a in tracker_db_interface_create_statement
(interface=0x806f0f0, query=0xb7fd5abc "SELECT \"%s\" FROM \"%s\"
WHERE ID = ?") at tracker-db-interface.c:291
#8  0xb7f9a67a in get_property_values (property=0x83c9800) at
tracker-data-update.c:761
#9  0xb7f9bb0d in delete_metadata_decomposed (property=0x83c9800,
value=0x8066270
"urn:nepomuk:datasource:9291a450-1d49-11de-8c30-0800200c9a66",
error=0x0)
    at tracker-data-update.c:982
#10 0xb7f9ca7b in tracker_data_delete_statement (subject=0x806e2d0
"file:///home/wena/work/easyview/logs/mule.log", predicate=0x83c9788
"http://purl.org/dc/elements/1.1/source";,
    object=0x8066270
"urn:nepomuk:datasource:9291a450-1d49-11de-8c30-0800200c9a66",
error=0x0) at tracker-data-update.c:1157
#11 0xb7f9cfe5 in tracker_data_delete_resource_description
(uri=0x806e2d0 "file:///home/wena/work/easyview/logs/mule.log",
error=0xbffff25c) at tracker-data-update.c:1798
#12 0xb7fb6995 in tracker_sparql_query_execute_drop_graph
(self=0x83ff340, error=0xbffff2d8) at tracker-sparql-query.c:2464
#13 tracker_sparql_query_execute (self=0x83ff340, error=0xbffff2d8) at
tracker-sparql-query.c:1157
#14 0xb7f9951f in tracker_data_update_sparql (
    update=0x84040c8 "DROP GRAPH
<file:///home/wena/work/easyview/logs/mule.log> INSERT
{\n<file:///home/wena/work/easyview/logs/mule.log> a
nfo:FileDataObject ;\n\t nfo:belongsToContainer
<file:///home/wena/work/easyview/log"..., error=0xbffff2d8) at
tracker-data-update.c:1838
#15 0x080533eb in queue_idle_handler (user_data=0x83f5110) at
tracker-store.c:203
#16 0xb7c5e0b1 in g_idle_dispatch (source=0x8410f10, callback=0,
user_data=0x83f5110) at
/build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gmain.c:4065
#17 0xb7c5fe98 in g_main_dispatch (context=0x80670b0) at
/build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gmain.c:1960
#18 IA__g_main_context_dispatch (context=0x80670b0) at
/build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gmain.c:2513
#19 0xb7c63623 in g_main_context_iterate (context=0x80670b0, block=1,
dispatch=1, self=0x805b850) at
/build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gmain.c:2591
#20 0xb7c63aea in IA__g_main_loop_run (loop=0x8402238) at
/build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gmain.c:2799
#21 0x080503f6 in main (argc=Cannot access memory at address 0x0
) at tracker-main.c:430


On Tue, Nov 3, 2009 at 15:21, Philip Van Hoof<spam pvanhoof be> wrote:
> Can you give us a new backtrace?
>
> On Tue, 2009-11-03 at 14:01 +0200, Tshepang Lekhonkhobe wrote:
> > On Tue, Nov 3, 2009 at 13:03, Tshepang Lekhonkhobe<tshepang gmail com> wrote:
> > > On Tue, Nov 3, 2009 at 12:50, Philip Van Hoof<spam pvanhoof be> wrote:
> > > > On Tue, 2009-11-03 at 11:48 +0100, Philip Van Hoof wrote:
> > > > > On Tue, 2009-11-03 at 12:46 +0200, Tshepang Lekhonkhobe wrote:
> > > > > > On Tue, Nov 3, 2009 at 12:04, Philip Van Hoof<spam pvanhoof be> wrote:
> > > > > > > We can't reproduce this problem. It would be useful if you guys could
> > > > > > > try to reproduce it after applying this patch:
> > > > > >
> > > > > > same crash; I'll do "tracker-control -r" and check again
> > > > >
> > > > > No, no need. Keep your situation if you can easily reproduce this way.
> > > > > We'll need it in a few moments to test against.
> > >
> > > silly me. I was too quick.
> > >
> > > > Can you try to reproduce against current master? We committed a fix for
> > > > this, but as we can't reproduce this ourselves you'll have to verify it.
> > >
> > > let's see if I can reproduce before I install the update; it's going
> > > to take a while; unless Laurent still got old DB around and checks
> > > this update
> >
> > I managed to reproduce even after a re-index, and even after
> > installing the update from master.
>
>
> --
> 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



-- 
my place on the web:
floss-and-misc.blogspot.com