Invalid length given for storage, got: 90 but expected: 64

Tile generation halts after several hundred tiles.

• Dynmap Version: dynmap v3.1-beta-2-389
• Server Version: Spigot 1.16.1

[09:37:10] [Dynmap Render Thread/INFO]: Full render of map 'flat' of 'world' in progress - 100 tiles rendered (92.35 msec/tile, 55.73 msec per render)^[[m
[09:37:18] [Dynmap Render Thread/INFO]: Full render of map 'flat' of 'world' in progress - 200 tiles rendered (85.99 msec/tile, 53.50 msec per render)^[[m
[09:37:25] [Dynmap Render Thread/INFO]: Full render of map 'flat' of 'world' in progress - 300 tiles rendered (78.82 msec/tile, 47.06 msec per render)^[[m
[09:37:33] [Dynmap Render Thread/INFO]: Full render of map 'flat' of 'world' in progress - 400 tiles rendered (75.78 msec/tile, 43.85 msec per render)^[[m
[09:37:40] [Dynmap Render Thread/INFO]: Full render of map 'flat' of 'world' in progress - 500 tiles rendered (74.18 msec/tile, 42.84 msec per render)^[[m
[09:37:46] [Dynmap Render Thread/INFO]: Full render of map 'flat' of 'world' in progress - 600 tiles rendered (72.44 msec/tile, 41.91 msec per render)^[[m
[09:37:53] [Dynmap Render Thread/INFO]: Full render of map 'flat' of 'world' in progress - 700 tiles rendered (71.22 msec/tile, 41.35 msec per render)^[[m
[09:37:59] [Dynmap Render Thread/INFO]: Full render of map 'flat' of 'world' in progress - 800 tiles rendered (69.70 msec/tile, 40.54 msec per render)^[[m
[09:38:06] [Dynmap Render Thread/INFO]: Full render of map 'flat' of 'world' in progress - 900 tiles rendered (70.30 msec/tile, 40.21 msec per render)^[[m
[09:38:15] [Dynmap Render Thread/INFO]: Full render of map 'flat' of 'world' in progress - 1000 tiles rendered (71.43 msec/tile, 40.81 msec per render)^[[m
[09:38:22] [Dynmap Render Thread/INFO]: Full render of map 'flat' of 'world' in progress - 1100 tiles rendered (71.51 msec/tile, 40.60 msec per render)^[[m
[09:38:30] [Dynmap Render Thread/ERROR]: [dynmap] Exception while fetching chunks:
java.lang.IllegalArgumentException: Invalid length given for storage, got: 90 but expected: 64
        at net.minecraft.server.v1_16_R1.DataBitsPacked.<init>(SourceFile:39) ~[mur_creative.jar:git-Spigot-0509002-7c03d25]
        at org.dynmap.bukkit.helper.v116.MapChunkCache115$NBTSnapshot.<init>(MapChunkCache115.java:220) ~[?:?]
        at org.dynmap.bukkit.helper.v116.MapChunkCache115.loadChunks(MapChunkCache115.java:449) ~[?:?]
        at org.dynmap.bukkit.DynmapPlugin$BukkitServer$6.call(DynmapPlugin.java:490) ~[?:?]
        at org.dynmap.bukkit.DynmapPlugin$BukkitServer$6.call(DynmapPlugin.java:477) ~[?:?]
        at org.bukkit.craftbukkit.v1_16_R1.scheduler.CraftFuture.run(CraftFuture.java:88) ~[mur_creative.jar:git-Spigot-0509002-7c03d25]
        at org.bukkit.craftbukkit.v1_16_R1.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:400) ~[mur_creative.jar:git-Spigot-0509002-7c03d25]
        at net.minecraft.server.v1_16_R1.MinecraftServer.b(MinecraftServer.java:1061) ~[mur_creative.jar:git-Spigot-0509002-7c03d25]
        at net.minecraft.server.v1_16_R1.DedicatedServer.b(DedicatedServer.java:354) ~[mur_creative.jar:git-Spigot-0509002-7c03d25]
        at net.minecraft.server.v1_16_R1.MinecraftServer.a(MinecraftServer.java:1009) ~[mur_creative.jar:git-Spigot-0509002-7c03d25]
        at net.minecraft.server.v1_16_R1.MinecraftServer.v(MinecraftServer.java:848) ~[mur_creative_.jar:git-Spigot-0509002-7c03d25]
        at net.minecraft.server.v1_16_R1.MinecraftServer.lambda$0(MinecraftServer.java:164) ~[mur_creative.jar:git-Spigot-0509002-7c03d25]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_212]

Uncertain if this should be marked as a duplicate since I couldn’t find similar issues related to Spigot 1.16.1.

[mikeprimm-triva]

I’m actually tempted to write a plugin to do the operation I suggested - it’s just not appropriate for Dynmap to do it, as I make a very major point of making sure Dynmap stays ‘read only’ in its role of processing world data. Frankly, don’t have the time to deal with hundreds of server folks blaming Dynmap for corrupting their world data… we already get blamed for every memory issue they encounter, because we’ve got a thread pool that includes labelled threads, so naturally every server crash is because of the fact that Dynmap’s name is somewhere in the thread dump…

I certainly can handle the un-processable chunk as a null chunk with a warning post.

[mikeprimm]

Fix was in 3.1-beta-3 - if anyone has a new report with that release (or, better, 3.1-beta-3a), open a new issue