Hi,
so all OSRM releases up to 5.2.7 work ok on my machine and with my
input file and the foot profile; all releases from 5.3.0 upwards have
the segfault. I'll continue trying to identify exactly where it was
introduced.
(It could of course still be a funny problem with 16.04 or with my input
Come to think of it, it would probably be simpler to just make each node
aware of the "highest" order of highway. Knowing that, it would work to
read that info for each constituent way and determine priority based on if
the way's order matches the node's order..
On Thu, Oct 6, 2016 at 1:29 AM,
Hi,
I've re-run with debug enabled but that wasn't much better:
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x77725)[0x7fd9e4134725]
/lib/x86_64-linux-gnu/libc.so.6(+0x7ff4a)[0x7fd9e413cf4a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7fd9e4140abc]
Hey Frederik,
the 5.4 release and its three profiles (car, foot, bike) work fine for us
on all our deployments, with the latest planet.
I think we need more details here: first of all, it seems like Ubuntu 16.04
ships Lua5.3 with apt, for which we saw an immense increase in memory usage.
This
This is not planned at the moment, since all the profiles know about are
tags. All additional processing has to happen internally in the C++ code,
and that's exactly why priority roads / give ways / stop signs are a bit
ugly to implement. Sorry.
On Thu, Oct 6, 2016 at 12:19 AM, Spencer Gardner
