java.lang.IllegalArgumentException

Hi, with the mkgmap sr1846 I see now this java exception: Exception in thread "main" java.lang.IllegalArgumentException at java.nio.ByteBuffer.allocate(ByteBuffer.java:311) at uk.me.parabola.imgfmt.sys.Directory.sync(Directory.java:176) at uk.me.parabola.imgfmt.sys.ImgFS.sync(ImgFS.java:230) at uk.me.parabola.imgfmt.sys.ImgFS.close(ImgFS.java:240) at uk.me.parabola.mkgmap.combiners.GmapsuppBuilder.onFinish(GmapsuppBuilder.java:119) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:413) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:126) at uk.me.parabola.mkgmap.main.Main.main(Main.java:127) Don't know if this is serious, at least the process finished and I get a map which works fine for my region. It's SUN Java 1.6.0_23-b05 It this something introduced with the last mkgmap changes, something broken in the OSM file or a problem with my config? Thanks, Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)

On 16/02/11 09:50, Thorsten Kukuk wrote:
Hi,
with the mkgmap sr1846 I see now this java exception:
Exception in thread "main" java.lang.IllegalArgumentException at java.nio.ByteBuffer.allocate(ByteBuffer.java:311) at uk.me.parabola.imgfmt.sys.Directory.sync(Directory.java:176) at uk.me.parabola.imgfmt.sys.ImgFS.sync(ImgFS.java:230) at uk.me.parabola.imgfmt.sys.ImgFS.close(ImgFS.java:240) at uk.me.parabola.mkgmap.combiners.GmapsuppBuilder.onFinish(GmapsuppBuilder.java:119) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:413) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:126) at uk.me.parabola.mkgmap.main.Main.main(Main.java:127)
Don't know if this is serious, at least the process finished and I get a map which works fine for my region. It's SUN Java 1.6.0_23-b05
It this something introduced with the last mkgmap changes, something broken in the OSM file or a problem with my config?
This is happening during writing out the gmapsupp.img file. It is unlikely that the file is complete even if it is slightly usable. I don't know what causes it, there are several possibilities for example if it is over 2G in size. But the last time it was reported that was not the problem. There was a recent thread here: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2011q1/010089.html ..Steve

On Wed, Feb 16, Steve Ratcliffe wrote:
On 16/02/11 09:50, Thorsten Kukuk wrote:
Hi,
with the mkgmap sr1846 I see now this java exception:
Exception in thread "main" java.lang.IllegalArgumentException at java.nio.ByteBuffer.allocate(ByteBuffer.java:311) at uk.me.parabola.imgfmt.sys.Directory.sync(Directory.java:176) at uk.me.parabola.imgfmt.sys.ImgFS.sync(ImgFS.java:230) at uk.me.parabola.imgfmt.sys.ImgFS.close(ImgFS.java:240) at uk.me.parabola.mkgmap.combiners.GmapsuppBuilder.onFinish(GmapsuppBuilder.java:119) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:413) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:126) at uk.me.parabola.mkgmap.main.Main.main(Main.java:127)
Don't know if this is serious, at least the process finished and I get a map which works fine for my region. It's SUN Java 1.6.0_23-b05
It this something introduced with the last mkgmap changes, something broken in the OSM file or a problem with my config?
This is happening during writing out the gmapsupp.img file. It is unlikely that the file is complete even if it is slightly usable.
Yes, that's what I expecdt.
I don't know what causes it, there are several possibilities for example if it is over 2G in size.
I'm far away from 2GB, currently it's about 900MB. I'm currently testing with different changes to find out what caused it. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)

On Wed, Feb 16, Thorsten Kukuk wrote:
Hi,
with the mkgmap sr1846 I see now this java exception:
Exception in thread "main" java.lang.IllegalArgumentException at java.nio.ByteBuffer.allocate(ByteBuffer.java:311) at uk.me.parabola.imgfmt.sys.Directory.sync(Directory.java:176) at uk.me.parabola.imgfmt.sys.ImgFS.sync(ImgFS.java:230) at uk.me.parabola.imgfmt.sys.ImgFS.close(ImgFS.java:240) at uk.me.parabola.mkgmap.combiners.GmapsuppBuilder.onFinish(GmapsuppBuilder.java:119) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:413) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:126) at uk.me.parabola.mkgmap.main.Main.main(Main.java:127)
Ok, if I run the tile splitter with --max-nodes=700000, I get this exception. But only for germany, haven't found any other country. With --max-nodes=1000000, it's working fine. Only problem: For some countrys, --max-nodes=1000000 is too much and mkgmap will abort ... Trying now IBM java 1.6.0, since I see heap corruption with SUN java sometimes which I never saw before when I used IBM java. Only disadvantage of IBM Java is, it is much slower (factor 6-10) than SUN java ... Between, using gmt to create a gmapsupp.img always works fine, even when mkgmap aborts with the above exception. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)
participants (2)
-
Steve Ratcliffe
-
Thorsten Kukuk