crash when move the player

[jarocajavi]

Yesterday after updating since 1.18.1 with all the mods tested... i guess at least... I see when i move in far zone using elytra crash the server, i try again with not elytra and the same.

In first instance i think the issue was with Dynmap, because was the new ones, so i removed, and same crash.

Im a few lost, can you help me with this?
crash-2022-03-11_21.07.37-server.txt

Thanks anyway!

Edit: something with lava?

[warjort]

java.lang.StackOverflowError: Exception while updating neighbours
	at net.fabricmc.loader.impl.launch.knot.KnotClassDelegate.getPostMixinClassByteArray(KnotClassDelegate.java:240)
	at net.fabricmc.loader.impl.launch.knot.KnotClassDelegate.tryLoadClass(KnotClassDelegate.java:150)
	at net.fabricmc.loader.impl.launch.knot.KnotClassLoader.loadClass(KnotClassLoader.java:155)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520)
	at org.apache.logging.log4j.message.ParameterizedNoReferenceMessageFactory.newMessage(ParameterizedNoReferenceMessageFactory.java:105)
	at org.apache.logging.log4j.message.AbstractMessageFactory.newMessage(AbstractMessageFactory.java:99)
	at org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:2057)
	at org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:1931)
	at org.apache.logging.log4j.spi.AbstractLogger.warn(AbstractLogger.java:2805)
	at org.apache.logging.log4j.spi.AbstractLogger.handleLogMessageException(AbstractLogger.java:2225)
	at org.apache.logging.log4j.spi.AbstractLogger.tryLogMessage(AbstractLogger.java:2208)
	at org.apache.logging.log4j.spi.AbstractLogger.logMessageTrackRecursion(AbstractLogger.java:2159)
	at org.apache.logging.log4j.spi.AbstractLogger.logMessageSafely(AbstractLogger.java:2142)
	at org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:2040)
	at org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:1907)
	at org.apache.logging.slf4j.Log4jLogger.warn(Log4jLogger.java:243)
	at net.minecraft.class_6396.method_37121(class_6396.java:83)
	at net.minecraft.class_6396.<init>(class_6396.java:51)
	at net.minecraft.class_128.<init>(class_128.java:32)
	at net.minecraft.class_128.method_560(class_128.java:264)

Can you post the log/latest.log?
The actual crash shown is in the classloading during the error reporting so this is not showing the original error.
class_128 is the crash reporting class

	at net.minecraft.class_1937.method_8492(class_1937.java:358)
	at net.minecraft.class_1937.method_8452(class_1937.java:321)
	at net.minecraft.class_3218.method_8408(class_3218.java:1377)
	at net.minecraft.class_1937.method_30092(class_1937.java:235)
	at net.minecraft.class_1937.method_8652(class_1937.java:196)
	at net.minecraft.class_1937.method_8501(class_1937.java:311)
	at net.minecraft.class_2404.method_10316(class_2404.java:140)
	at net.minecraft.class_2404.method_9612(class_2404.java:126)
	at net.minecraft.class_4970$class_4971.method_26181(class_4970.java:884)
	at net.minecraft.class_1937.method_8492(class_1937.java:356)
	at net.minecraft.class_1937.method_8452(class_1937.java:321)
	at net.minecraft.class_3218.method_8408(class_3218.java:1377)
	at net.minecraft.class_1937.method_30092(class_1937.java:235)
	at net.minecraft.class_1937.method_8652(class_1937.java:196)
	at net.minecraft.class_1937.method_8501(class_1937.java:311)
	at net.minecraft.class_2404.method_10316(class_2404.java:140)
	at net.minecraft.class_2404.method_9612(class_2404.java:126)
	at net.minecraft.class_4970$class_4971.method_26181(class_4970.java:884)

This part which is probably the real crash, shows minecraft in a recursive loop during block updates.
Like you say, further down it shows the blocks being updated are lava blocks.

From what I can see, there is no mention of any modded code so this could be a vanilla minecraft bug?

It could also be a mod changing the behaviour, but doing it in a way that does not show up in the stacktrace.
If that is the case, there is no way to tell which mod from this error, but there maybe something in the log?

[warjort]

One thing to test, is whether you get the same problem in a vanilla minecraft world with the same seed when you go to that spot "-3753,-55,-822".
If you do, then you should report it to Mojang.

[warjort]

This known and unresolved vanilla bug looks similar to your report?
https://bugs.mojang.com/browse/MC-248200

[jarocajavi]

Hello! Im sorry for the wait... And thanks for the help, finally i had restore a backup and work fine, remove dynmap, maybe the issue was like u say from mojang, but for now i fix it, the log.file is gone, i removed all folder after see all works good, but the nex time happen to me i'll shared too.

Thanks again, and close this for now. :\