Corrupted Heightmap Data (?)

So I recently moved providers (from Oracle to EnviroMC), but I noticed my server sometimes will crash. It seems to be an out of memory thing but afiak I have enough memory (10gb at 350mods and max like 5 players) I do see this message spammed alot tho [21:33:39] [Server thread/WARN] [minecraft/Heightmap]: Ignoring heightmap data for chunk [X, Y], size does not match; expected: 52, got: 37 X and Y tends to be around world spawn but its almost any coord in the world. Usually spams a bunch from one chunk at a time. I'm worried this is causing a memory leak which is eventually causing a server crash. If this is an issue, I'm wondering if I can mass edit the heightmap data to convert everything from 52 to 37? Every single time this happens, it says it got "37"
No description
4 Replies
Priority6
Priority6OP4w ago
Its not a constant spam, but it does happen whenever you go into different chunks it seems like The chunk you go in does not seem to correlate with the coords appearing on the logs Forge 1.20.1 47.3.12
Priority6
Priority6OP4w ago
Ignoring heightmap data for chunk xx warning in console - Admincraft
So basically, the server logs will get spammed by the following: ```[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 28], size does not match; expected: 37, got: 52 [21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 29], size does not match; expected: 37, got: 52 [21:19:05] [Server thread/WARN]: Ignor...
Priority6
Priority6OP4w ago
Seems like adding a few jvm flags used when migrating versions to force update and clear cache did fix it (?)
No longer seeing the console spam
Seems like adding a few jvm flags used when migrating versions to force update and clear cache did fix it (?)
No longer seeing the console spam
Just wondering what specific jvm flags i could use, and how i would go about clearing cache these are my current startup settings From the panel:
java $([[ -f user_jvm_args.txt ]] && printf %s "@user_jvm_args.txt") -Xms128M -Xmx10240M -Dterminal.jline=false -Dterminal.ansi=true -XX:+AlwaysPreTouch -XX:+DisableExplicitGC -XX:+ParallelRefProcEnabled -XX:+PerfDisableSharedMem -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1HeapRegionSize=8M -XX:G1HeapWastePercent=5 -XX:G1MaxNewSizePercent=40 -XX:G1MixedGCCountTarget=4 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1NewSizePercent=30 -XX:G1RSetUpdatingPauseTimePercent=5 -XX:G1ReservePercent=20 -XX:InitiatingHeapOccupancyPercent=15 -XX:MaxGCPauseMillis=200 -XX:MaxTenuringThreshold=1 -XX:SurvivorRatio=32 -Dusing.aikars.flags=https://mcflags.emc.gs -Daikars.new.flags=true $([[ ! -f unix_args.txt ]] && printf %s "-jar `cat .serverjar`" || printf %s "@unix_args.txt")
java $([[ -f user_jvm_args.txt ]] && printf %s "@user_jvm_args.txt") -Xms128M -Xmx10240M -Dterminal.jline=false -Dterminal.ansi=true -XX:+AlwaysPreTouch -XX:+DisableExplicitGC -XX:+ParallelRefProcEnabled -XX:+PerfDisableSharedMem -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1HeapRegionSize=8M -XX:G1HeapWastePercent=5 -XX:G1MaxNewSizePercent=40 -XX:G1MixedGCCountTarget=4 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1NewSizePercent=30 -XX:G1RSetUpdatingPauseTimePercent=5 -XX:G1ReservePercent=20 -XX:InitiatingHeapOccupancyPercent=15 -XX:MaxGCPauseMillis=200 -XX:MaxTenuringThreshold=1 -XX:SurvivorRatio=32 -Dusing.aikars.flags=https://mcflags.emc.gs -Daikars.new.flags=true $([[ ! -f unix_args.txt ]] && printf %s "-jar `cat .serverjar`" || printf %s "@unix_args.txt")
From the user_jvm_args.txt file:
-Xms4G
-Xmx6G
-XX:+UseG1GC
-XX:+ParallelRefProcEnabled
-XX:MaxGCPauseMillis=200
-XX:+UnlockExperimentalVMOptions
-XX:+DisableExplicitGC
-XX:+AlwaysPreTouch
-XX:G1NewSizePercent=30
-XX:G1MaxNewSizePercent=40
-XX:G1HeapRegionSize=8M
-XX:G1ReservePercent=20
-XX:G1HeapWastePercent=5
-XX:G1MixedGCCountTarget=4
-XX:InitiatingHeapOccupancyPercent=15
-XX:G1MixedGCLiveThresholdPercent=90
-XX:G1RSetUpdatingPauseTimePercent=5
-XX:SurvivorRatio=32
-XX:+PerfDisableSharedMem
-XX:MaxTenuringThreshold=1
-Xms4G
-Xmx6G
-XX:+UseG1GC
-XX:+ParallelRefProcEnabled
-XX:MaxGCPauseMillis=200
-XX:+UnlockExperimentalVMOptions
-XX:+DisableExplicitGC
-XX:+AlwaysPreTouch
-XX:G1NewSizePercent=30
-XX:G1MaxNewSizePercent=40
-XX:G1HeapRegionSize=8M
-XX:G1ReservePercent=20
-XX:G1HeapWastePercent=5
-XX:G1MixedGCCountTarget=4
-XX:InitiatingHeapOccupancyPercent=15
-XX:G1MixedGCLiveThresholdPercent=90
-XX:G1RSetUpdatingPauseTimePercent=5
-XX:SurvivorRatio=32
-XX:+PerfDisableSharedMem
-XX:MaxTenuringThreshold=1
i realize now there are some duplicates, but this occured before i used the jvm arguments Overall, is this something I should be worried about?
Ternzeeh
Ternzeeh2w ago
Bump. What exact jvm arguments were used to fix this warning spam? Also having this on my modded server after adding Higher Heights datapack to my existing world. Bump again. Replaced my old jvm arguments with solely aikar's flags and that removed the console spam

Did you find this page helpful?