Have tried searching other issues, closest potential copy would be #4379, though that issue doesn't have a crash log to compare.

crash-2024-03-04_23.11.24-server.txt

Error: ServerHangWatchdog detected that a single server tick took 60.00 seconds

Crab function being called is m213651 which translates to updateDynamicGameEventListener on entity.

Version: 1.19.2
build: Quark-3.4-418.jar
forge: 1.19.2-43.3.5

Just encountered an identical issue on my own server. Same version, same build, running off of Forge 1.19.2-43.3.8
crash-2024-03-09_06.44.21-server.txt

got a similar issue on a 1.20.1 forge: 47.2.23
Server Crash Logs;
crash-2024-04-17_18.02.17-server.txt

I am getting this error on a very light pack on a server for 1.20.1
(basically just quark for features)
Quark-4.0-439.jar
Forge: 1.20.1-47.2.23

crash-2024-04-16_17.37.19-server.txt

This bug is a critical showstopper!

Quark cannot be used on any community server as it crashes the whole server.

All versions with this code should be marked as broken on both CurseForge and Modrinth.
If the bug is hard to solve, at least remove Crabs all together until a fix is found.

This is an unsustainable situation.

I have encountered the same bug, both on single player and on dedicated server.
It happens suddenly, while walking or flying through the world.

Minecraft 1.20.1
Forge 47.3.5
Quark 4.0-458

Crash log from the dedicated server:
crash-2024-08-01_04.48.13-server.txt

If it is of any help:

Quark versions failing spans from 3.4-418 to 4.0-458.
Forge versions used spans from 43.3.5 to 47.3.5

All the crash reports fail on the m_213651 in ...org.violetmoon.quark.content.mobs.entity.Crab.m_213651_...

In the above 5 crash reports, the only mods that are present in all of them are:

• architectury
• balm
• betterchunkloading
• Clumps
• cupboard
• ferritecore
• jei
• journeymap
• Quark
• smoothchunk

That rules out Canary and ModernFix as culprits.

Can we get a critical and a crash label on this issue too?

Another user got this and happened to catch it with Spark, so here's the .sparkprofile (zipped) 9dgqISchuI.zip

The crab updateDynamicGameEventListener method is to the best of my knowledge exactly the same as Allay and Warden code, which also use the game event system in an identical way.

This user also had "betterchunkloading" and "smoothchunk". "Better chunk loading" has historically been the cause of a bunch of deadlocks.

I have boiled the issue down to a compat issue with betterchunkloading.

I got it to happen at some time with only quark and betterchunkloading installed (I somehow managed to forget to save the log, but I saw the org.violetmoon.quark.content.mobs.entity.Crab.m_213651_ in the log.

@quat1024 mentions that "Better chunk loading" has historically been the cause of a bunch of deadlocks., so the arrow is pointing in their direction.

Someone should go there and fill a bug report. I am too tired for today to do it.

I removed BCL a while ago and stopped getting this (but had forgotten about my original issue). It was also the cause of massive chunk loading lag in my packs. It's an interesting idea in theory, but in practice it's a hot mess.