My current server is running 1.12.2 just fine. When I try updating it to 1.13-pre6, it will eventually stop ticking when converting some chunks, long enough for the watchdog to kick in, shutting down the server.
One area of the world seems to be more affected than others. It is located at about x:600, z:-200.
Note: Mojang (Grumm) is already aware of the issue, and already have a copy of my world since June 4th, 2018 (a month ago).
Attachments
Comments 12
@Fabian Röling
Doing so will make it public, which I try to avoid. Is there any way to send you a link privately here?
Why would you need to keep it private?
Mail address is (a bit bot protected, you have to put the pieces together)
fabianroeling -
@ -
googlemail -
. -
com -
But of course it's way better to post the link here, that way more people can try to reproduce it.
@Fabian Röling
I want to keep it private cause it's a server world. I wouldn't like my people to download it, get the seed, locate stuff etc.
Link should be in your email, if I got it right!
I was as close to 600 -200 as possible (there's a house in the way). The game froze a bit multiple times when going there, but it calmed down again, no crash, no complete stop.
And yes, the server is still ticking, I know that thanks to the new F3 display "server at [...] ms/tick". For 120, this means that the game is running at less than half speed, but it is running. And that was 32 chunks on a laptop.
I had some pretty bad tps before, even more than 60 seconds per tick, but not in that world.
32 chunks and no stopping? Running as a server or single player? I can reproduce it on 3 machines, with 100% failure (one is a dedicated host, I don't know the exact specs), at only 10 chunks (server default). The only way I can make it without the server stopping is to reduce view distance to 1 or 2 chunks, and advance toward those coords, very slowly, chunk by chunk.
— I had some pretty bad tps before, even more than 60 seconds per tick, but not in that world
You cannot get more than 60 seconds per tick on a server. Watchdog will kick in and shut down the server. This is the problem I'm experiencing. This is due to how slow 1.13 converts old chunks to the new format. Mojang reproduced the problem, and are working on a fix that should come out today.
If one chunk takes 13 secs to convert and load, then you only need 5 similar chunks to trigger the watchdog. On a 10 chunks view distance, more than 400 chunks are loading.
What I may suggest you try:
Reload this world (new from the .zip) in 1.12.2. Teleport to 640 81 -192. Close world. Run it in a 1.13-pre8 server. Log back in. If problem doesn't show up, resolve this ticket as related to MC-132135.
Thanks for your help!
Watchdog doesn't necessarily shut down servers with over 60s ticks; that's only the default option. It can be raised, lowered, or even disabled entirely.
The next prerelease should in theory fix this issue, because chunk conversion will no longer happen on the fly, and instead will all be handled on initial load.
We learn something new every day! I thought at first that it was some undocumented feature and there I see "max-tick-time=60000" in the server.properties file... Remind me to slap my own face when I say silly stuff!
— The next prerelease should in theory fix this issue, because chunk conversion will no longer happen on the fly, and instead will all be handled on initial load.
Really? Grum told me they managed to get the conversion time down by a factor of 4 but should be even quicker after all optimizations. But I'm all for a "convert-on-world-load" solution. I think it's even better, in fact.
After further testing, this issue may be related to, or caused by MC-132135