Closed easbar closed 5 years ago
Thanks!
A probably better fix would be to implement this whole "check which virtual edge goes in which direction" logic in core without having to traverse virtual edges until we meet a real node in the first place
:+1: and probably avoid recursion and only create 2 EdgeExplorers.
This is the minimal fix for the infinite recursion discussed in #161 : We need to create a new edge explorer in each step of the recursion and turn off query graph cache. I do not think this has performance implications, because we are only traversing a few (in many cases probably just one) virtual edges and with core-1.0-pre4 query graph cache no longer improves performance anyway: https://github.com/graphhopper/graphhopper/pull/1751#discussion_r338244055
A probably better fix would be to implement this whole "check which virtual edge goes in which direction" logic in core without having to traverse virtual edges until we meet a real node in the first place.