Hi, AFAIK there should be no way for a java program to crash the JVM. So in any case a crash of the JVM is a problem of the JVM and not of the java program. So there is no chance for splitter to avoid such a crash. Please check if your 64bit JVM is installed correctly. WanMil
Hi,
I'm creating maps for Europe, which is a big piece of data. Splitting it is a main problem. I'm using Windows 7 x64 and recent splitter 306. My experiences are following:
Splitter on java 32bit and standard settings can split Europe.
If I add contours data to Europe file, splitter on java 32 fails because of not enough memory, i can use maximum -Xmx1600M.
Any use of splitter on java 64bit most probably will crash java VM. Usually this happens after 1 hour of work, often when starting processing second set of areas. I have many logs form crashes, but don't know how useful it could be. Logs contains info like: # JRE version: 7.0_21-b11 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode windows-amd64 compressed oops) # Problematic frame: # J java.util.HashMap.put(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
# Problematic frame: # J java.util.HashMap.containsKey(Ljava/lang/Object;)Z
# Problematic frame: # V [jvm.dll+0x360038]
# Problematic frame: # j java.util.AbstractCollection.toArray([Ljava/lang/Object;)[Ljava/lang/Object;+88
# Problematic frame: # J uk.me.parabola.splitter.BinaryMapWriter$PBFSerializer$Prim.addStringsToStringtable()V
Splitting contours created for Europe by pphyghtmap with default settings usually fails. I have changed max-nodes-per-way form default 2000 to 500 which allowed splitter to finish this task.
I understand that it is java x64 which crashes. But since 32bit version is already too limited to process big data, wouldn't be good to investigate this problem? Maybe you could make spliter compatible with 64bit version.