[0.2.32] Specific world generation breaks server and SP
pschwippert opened this issue ยท 11 comments
I have encountered a reproducible bug in my world on ATM-7 0.2.32.
The world completely hangs, this happens in both Single player and on my server. Something causes the server to freeze irriversibly when a specific chunk is loaded.
Steps to reproduce:
- Make a world (in creative) with this seed: -5832385100026085854
- Teleport to 3063 139 -5056
- Fly East
Suddenly any and all chunks will stop loading, chat will halt, no commands can be issued. On my server all players get kicked with a time out. Checking the logs yields nothing out of the ordinary. What I initially assumed is that it was just having a hard time loading but the server had 0% CPU usage and no changes in memory usage.
In single player I found that while I don't get auto kicked, when I try save and exit to main menu, the game gets stuck on "Saving World".
I have tried my best to try identify what exactly might be causing this but unfortunately this is all the information I currently have. Could anyone verify is this is reproducible?
it might be a vanilla minecraft thing and probably get fixed in 1.18.2 as patchnotes of 1.18.2-RC1 read:
"MC-244682 โ Some custom dimensions settings can cause the server to stop running, but not crash."
"MC-248764 โ Some worldgen datapacks can kill the internal server (possibly related to density functions)."
โ from https://minecraft.fandom.com/wiki/Java_Edition_1.18.2_Release_Candidate_1
So the server scripts stop so bad, that even the maximum tick time check and log does work anymore.
I was about to ask you to do a check with simulation distance 1 (or whatever minimum) and a far view distance. nice ^^
So... What happens on generation?
First basic terrain generation and generation of special places. Then or only on first accessing the chunk it will get populated and only inside the simulation distance the AI shall start working.
can you check with sim distance 1 and whatever view distance 12 or 16 oder even higher?
Then I assume you shall be able to look over the meteroit and it shall only crash once you are 1 chunk nearby.
if it crashes earlier then its still sth inbetween generation and simulation.
if it crashes only when you are ontop of it, then its simulation.
It might be a coincidence - like in the other issue, where the creator thought it is the outpost.
It is possible, that mods try to generate stuff ontop of each other and cause problems tho...
Okay so I did some more tests
- approaching from the other side also crashes the game, the side I am approaching from now is already the other side haha
- Somehow.... magically... I remade the world and when I teleported directly on top of the coords 3227 64 -4978 it didn't crash, it generated the whole meteor. When doing this on my server it also worked...?
So while it's nice that it seems to have "fixed" itself, this is extremely weird and am at a loss what is causing it...
oh my... very weird... does not make it easier tho.
hostiles wont spawn if the player is too close
this is #228 with a (much) better title
can confirm!
I did not reevaluate the seeds in 0.2.34 yet (latest ATM7 0.2.35 is unplayable with its own new issue anyway)
We know additional 3 seeds where for sure at a given position the world gen will crash all server scripts (since 0.2.20b):
- "237475516696349671" (0.2.32 still)
/teleport @p 800 190 1200 0 20
go 400 south (from @RyanP1991) - "7360393597478526904" (0.2.32 still)
/teleport @p 0 190 600 0 20
go 400 south (from @Eld0r) - "-4005908143735417944" (0.2.32 still)
/teleport @p -450 190 1200 0 20
go 400 south (from @Annonymouse8)
this one got somehow fixed in newer ATM7 - I checked that seed in 0.2.32 without problems on this position):
- "7959206620129908431" (only 0.2.19)
/teleport @p -2720 190 1536 90 20
go 600 west (from @Jiggshaha)
Okay so there are multiple seeds that are causing these isssues... Do you know of the common denominator between these seeds? What is it trying to load?
I think it has to do with loading specific chunks, I am going to try forcing generation of the chunks using /forge generate on the server and will report back if it's the generation side or it's the loading of the chunk that crashes the server in this way
I have made a new world in SP and did /forge generate 3050 64 -5056 2500
to generate all the chunks around that point hoping that that may have solved the issue.
Unfortunately it did not solve the issue, so my guess is that this happens when loading the chunk, not upon generating the chunk. I will attach a screenshot of my Journeymap roughly where I think it happens