Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

With turn costs something requires a lot more memory on import

See original GitHub issue

If I just want to import a city (~50MB source map) and import this with car, without turn costs and 1g RAM, then all is fine. But with turn_costs=true the import fails with:

2016-12-21 10:48:31,271 [main] INFO  com.graphhopper.reader.osm.GraphHopperOSM - using car|RAM_STORE|2D|turn_cost|,,,,, memory:totalMB:981, usedMB:46
Exception in thread "pool-3-thread-2" java.lang.OutOfMemoryError: GC overhead limit exceeded
	at com.graphhopper.reader.ReaderElement.<init>(ReaderElement.java:40)
	at com.graphhopper.reader.ReaderNode.<init>(ReaderNode.java:42)
	at com.graphhopper.reader.osm.pbf.PbfBlobDecoder.processNodes(PbfBlobDecoder.java:238)

As the overhead of turn costs should be neglectable and the import itself should work with <500MB this seems to be a bug.

See also “Why do we have static edge and node IDs” #556

Issue Analytics

State:
Created 7 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

karussellcommented, Jan 19, 2017

We have to remove this warning, as large PBFs seem to have large blobs …

1reaction

karussellcommented, Jan 18, 2017

The workaround was regarding the higher memory consumption. The underlying issue is that your pbf (as well as my example) seem to have several times bigger blobs than usual which causes a very high memory requirement, but this is only strange for small areas. So it might be good to avoid this warning completely.