-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Asserting during map-matching when core factor used #3969
Comments
@daniel-j-h possibly, except that is during path unpacking (after routing is complete), this one is happening during routing. They're both related to self loops though, so fixing one might fix them both. |
Here is the analysis for another abort. The problem is that data is ephemeral and it is not possible to find out exact graph weights now, so i made an assumption about the edge that could potentially lead to the abort. The input phantom nodes at are
The abort happened at with the following state of the stack
From the heap data This can happen with the following steps:
EDIT: it is not really possible to reproduce the issue without data, but there are two possibilities:
|
Is this still a concern as we're considering deprecating CoreCH? |
Agreed, I think we can let this go and assume it will disappear once CoreCH is gone. Closing as WONTFIX. |
Every now and again, we see an assertion being thrown during map-matching:
`bt full` leading up to assertion
Which is this: https://github.com/Project-OSRM/osrm-backend/blob/5.6/src/engine/routing_algorithms/routing_base.cpp#L430-L431
This trace is from OSRM 5.6.4.
This looks like it's a different issue to #3647, but as it also touches self-loops, I wonder if it's not a related problem.
The text was updated successfully, but these errors were encountered: