When creating two (or more) maps in parallel that produce JPEGs, at least one will crash with below execption.
It seems some thread data is mixed up somehow. Looking into the code, I could not find a smoking gun, though.
java.lang.IllegalStateException: Attempt to use instance of com.sun.imageio.plugins.jpeg.JPEGImageWriter@24cded50 locked on thread Thread[AtlasThread 4,6,main] from thread Thread[AtlasThread 3,6,main]
at com.sun.imageio.plugins.jpeg.JPEGImageWriter.setThreadLock(Unknown Source)
at com.sun.imageio.plugins.jpeg.JPEGImageWriter.write(Unknown Source)
at mobac.program.tiledatawriter.TileImageJpegDataWriter.processImage(TileImageJpegDataWriter.java:107)
at mobac.program.atlascreators.tileprovider.ConvertedRawTileProvider.getTileData(ConvertedRawTileProvider.java:48)
at mobac.program.atlascreators.AbstractSQLite.createTiles(AbstractSQLite.java:105)
at mobac.program.atlascreators.RMapsSQLite.createMap(RMapsSQLite.java:97)
at mobac.program.AtlasThread.createMap(AtlasThread.java:360)
at mobac.program.AtlasThread.createAtlas(AtlasThread.java:205)
at mobac.program.AtlasThread.run(AtlasThread.java:122)
Thanks for reporting this issue. Could you please add more info on your OS and the used Java-VM?
Last edit: r_x 2018-09-04
This is under W10, but also happened under W7, if I recall correctly /# of maps was smaller back then, so I took the pain :-)
java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 1.8.0_161-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode)
BTW: it needs larger map generation runs to produce the error. Each one producing 500 MB+ maps should do.
One more (off topic) thing: could this be interesting re. missing labels ?
https://github.com/mapsforge/mapsforge/commit/6f8312f43724a84ccc1dbc962dbeb7a0c076061e
BINGO - works like a charm. TXs a lot, Robert!