Some sort of world corruption or something that causes a data leak. Whenever the chunks around (3000, 3000) are rendered in the data leak (idk if thats the correct term) begins. The world basically stops though, breaking blocks doesnt actually do anything besides make the block disappear, commands stop doing stuff, etc. When you leave the game gets stuck on saving world, and after closing Minecraft and reopening the world, you end up a few seconds before you rendered the chunks. For some context as to the contents of the region, it was a mini game that worked fine until it didnt and started doing that. It has command blocks and structure blocks. We have tried solving this in multiple ways, we have disabled stuff like command blocks, we have also tried deleting the chunks with outside tools and the problem persists. And as it just causes the game to die, it's not really possible to actually know what the problem is.
Steps to reproduce:
Import and open the linked world
Teleport to 3000 100 3000:
/tp 3000 100 3000
Observed result:
The server seems to freeze and there is a memory leak.
Expected result:
The game functions normally.
I was able to reproduce the server-thread freeze when loading the world locally, but not a memory leak. Task manager does not show RAM usage going up, and in fact sometimes shows RAM usage drop suddenly by 300 MB or so. Disabling addons (which also removes the ticking areas) lowering simulation and render distance does not prevent the crash. The affected area of this world is in a ticking area when the world is opened with the addons enabled, so it must be something triggered by the client when loading those chunks that causes the server thread to freeze and/or crash.