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.

To little RAM in Graph Processing leads to weird Exception in LocationIndex

See original GitHub issue

I’ve been playing around with GH for a while now and everything worked fine so far, until I tried building the latest and greatest all new and shiny graph of all of Europe with my little 16 GB machine (Mac OS) with 14Gb allocated for the JVM, when it was throwing the following error

2017-06-07 13:42:10,958 [main] INFO  com.graphhopper.reader.osm.GraphHopperOSM - edges: 69505872, nodes 54314626, there were 2119927 subnetworks. removed them => 2119847 less nodes
Exception in thread "main" java.lang.IllegalStateException: location index was opened with incorrect graph: 54314817 vs. 54314626
	at com.graphhopper.storage.index.LocationIndexTree.loadExisting(LocationIndexTree.java:265)
	at com.graphhopper.GraphHopper.createLocationIndex(GraphHopper.java:1134)
	at com.graphhopper.GraphHopper.initLocationIndex(GraphHopper.java:1149)
	at com.graphhopper.GraphHopper.postProcessing(GraphHopper.java:842)
	at com.graphhopper.GraphHopper.process(GraphHopper.java:650)
	at com.graphhopper.GraphHopper.importOrLoad(GraphHopper.java:619)
	at com.graphhopper.tools.Import.main(Import.java:31)

The error is included in GH versions 0.82 and 0.9. It did not appear when I ran the whole process on a 64GB Ubuntu 16.04. Server on which it was using more then 26GB.