oqgraph-dev team mailing list archive
-
oqgraph-dev team
-
Mailing list archive
-
Message #00218
[Bug 1133093] Re: Crash on ORDER BY in OQGRAPH v3
Back to an assertion crash still happening at exit, a bit more detective
work:
Assertion: inited on `edges` (backing store) not clearing to zero before
close. SO memory breakpoint on my_isam inited.
Looks like for some reason the matching ha_index_end never gets called
after seek_to initialises.
Downstream from graphcore.cc:768 case DIJKSTRAS | HAVE_ORIG | HAVE_DEST
Ultimately, it looks like
oqgraph_shim.h:292
oqgraph3::cursor*
end= new oqgraph3::cursor(const_cast<oqgraph3::graph*>(&g));
oqgraph3::cursor*
start= new oqgraph3::cursor(const_cast<oqgraph3::graph*>(&g));
start->seek_to(v, boost::none); <-- never has a corresponding path which calls ha_index_end
return std::make_pair(
graph_traits<oqgraph3::graph>::out_edge_iterator(start),
graph_traits<oqgraph3::graph>::out_edge_iterator(end));
--
You received this bug notification because you are a member of OQgraph
developers, which is a bug assignee.
https://bugs.launchpad.net/bugs/1133093
Title:
Crash on ORDER BY in OQGRAPH v3
Status in OQGraph Engine for MariaDB:
Triaged
Bug description:
SELECT * FROM graph WHERE latch=1 AND origid=1 AND destid=6;
works
SELECT * FROM graph WHERE latch=1 AND origid=1 AND destid=6 ORDER BY seq;
segfaults.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oqgraph/+bug/1133093/+subscriptions
References