I've taken a 1.12.2 world and tried to start it up under 1.13.pre6.
It starts ok, and runs hot (300%+ CPU) for 2 minutes, eventually outputting
[19:30:01] [Server thread/INFO]: Preparing spawn area: 100%
[19:30:01] [Server thread/INFO]: Time elapsed: 125724 ms
[19:30:01] [Server thread/INFO]: Done (126.673s)! For help, type "help"
But when I login, it spikes back up to 350% CPU, and takes a while to show terrain. I didn't move, just sat and waited for the CPU to drop back off, but eventually it crashed.
I ran the same world under pre5, and I could login and move around without a crash (suffered from TPS issues, but not this)
Attachments
Comments
migrated
migrated
Dunno, pre5 was fine.
Well.. it suffered from no iron golems and a slow TPS, but I could login and move around, CPU stayed at 50-10% and didn't crash.
I think this is new.
migrated
The behaviour in pre7 is a bit different. It still takes 2minutes to go from
[12:18:51] [Server thread/INFO]: Preparing start region for level 0
[12:20:52] [Server thread/INFO]: Preparing spawn area: 0%
but the CPU rans less intensively.
I was able to login but it was very slow in areas where chunks already existed, and eventually crashed. I started the server again, and logged in and it crashed immediately. I got a fresh copy of the world and tried again - I was able to go to the same location (walking instead of flying) and move around without a crash, but after visiting other 1.12.2 generated chunks, it crashed again.
I restarted the server, got another player to login at a different location and it crashed also.
I'll attach various crash logs from today (pre7)
migrated
The first crash seems to be an issue with the WorldGen pool? And then maybe its in a weird state and crashes?
migrated
pre8 - same behaviour except it took longer to get it to crash. I had to fly around fast in creative in known complicated areas.
Once its crashed once, you cannot login again, because the server times out.
[22:33:56] [Server Watchdog/FATAL]: A single server tick took 60.82 seconds (should be max 0.05)
[22:33:56] [Server Watchdog/FATAL]: Considering it to be crashed, server will forcibly shutdown.
But I fiddled server properties and set the
max-tick-time=600000
to see what might happen.
[22:41:17] [Server thread/ERROR]: Something went wrong upgrading!
java.lang.OutOfMemoryError: Java heap space
at hd.c(SourceFile:50) ~[minecraft_server.pre8.jar:?]
at hd.b(SourceFile:10) ~[minecraft_server.pre8.jar:?]
at gy.f(SourceFile:395) ~[minecraft_server.pre8.jar:?]
at gy.b(SourceFile:28) ~[minecraft_server.pre8.jar:?]
at he.c(SourceFile:271) ~[minecraft_server.pre8.jar:?]
at he.b(SourceFile:17) ~[minecraft_server.pre8.jar:?]
at gy.f(SourceFile:395) ~[minecraft_server.pre8.jar:?]
at gy.b(SourceFile:28) ~[minecraft_server.pre8.jar:?]
at hj.a(SourceFile:160) ~[minecraft_server.pre8.jar:?]
at hj.mergeInto(SourceFile:22) ~[minecraft_server.pre8.jar:?]
at com.mojang.datafixers.types.DynamicOps.set(DynamicOps.java:162) ~[minecraft_server.pre8.jar:?]
at com.mojang.datafixers.types.DynamicOps.lambda$update$11(DynamicOps.java:166) ~[minecraft_server.pre8.jar:?]
at com.mojang.datafixers.types.DynamicOps$$Lambda$1638/1344684320.apply(Unknown Source) ~[?:?]
at java.util.Optional.map(Optional.java:215) ~[?:1.8.0_171]
at com.mojang.datafixers.types.DynamicOps.update(DynamicOps.java:166) ~[minecraft_server.pre8.jar:?]
at com.mojang.datafixers.Dynamic.lambda$update$12(Dynamic.java:151) ~[minecraft_server.pre8.jar:?]
at com.mojang.datafixers.Dynamic$$Lambda$1636/1157730944.apply(Unknown Source) ~[?:?]
at com.mojang.datafixers.Dynamic.map(Dynamic.java:42) ~[minecraft_server.pre8.jar:?]
at com.mojang.datafixers.Dynamic.update(Dynamic.java:151) ~[minecraft_server.pre8.jar:?]
at zu.a(SourceFile:29) ~[minecraft_server.pre8.jar:?]
at zu$$Lambda$547/621337084.apply(Unknown Source) ~[?:?]
at com.mojang.datafixers.DataFix.lambda$null$2(DataFix.java:42) ~[minecraft_server.pre8.jar:?]
at com.mojang.datafixers.DataFix$$Lambda$1468/1907584040.apply(Unknown Source) ~[?:?]
at com.mojang.datafixers.FunctionType$$Lambda$1450/1016980185.apply(Unknown Source) ~[?:?]
at com.mojang.datafixers.FunctionType$Instance.lambda$first$2(FunctionType.java:84) ~[minecraft_server.pre8.jar:?]
at com.mojang.datafixers.FunctionType$Instance$$Lambda$1457/369384969.apply(Unknown Source) ~[?:?]
at com.mojang.datafixers.FunctionType$$Lambda$1450/1016980185.apply(Unknown Source) ~[?:?]
at com.mojang.datafixers.FunctionType$Instance.lambda$null$0(FunctionType.java:76) ~[minecraft_server.pre8.jar:?]
at com.mojang.datafixers.FunctionType$Instance$$Lambda$1456/1517960227.apply(Unknown Source) ~[?:?]
at com.mojang.datafixers.FunctionType$$Lambda$1450/1016980185.apply(Unknown Source) ~[?:?]
at com.mojang.datafixers.FunctionType$Instance.lambda$null$4(FunctionType.java:96) ~[minecraft_server.pre8.jar:?]
at com.mojang.datafixers.FunctionType$Instance$$Lambda$1510/1881320200.apply(Unknown Source) ~[?:?]
[22:41:29] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 315280ms or 6305 ticks behind
but it didn't crash. I have now logged in and can interact with the game. Until the next time this happens. I don't really want to leave the server with such a huge max tick time.
migrated
Flew around fast over built up areas.
[08:19:30] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 18355ms or 367 ticks behind
[08:19:51] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 5929ms or 118 ticks behind
[08:21:26] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 80632ms or 1612 ticks behind
[08:21:45] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 4187ms or 83 ticks behind
[08:22:36] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 35475ms or 709 ticks behind
[08:23:38] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 46850ms or 937 ticks behind
[08:24:05] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 2051ms or 41 ticks behind
[08:24:22] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 2057ms or 41 ticks behind
[08:25:11] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 2069ms or 41 ticks behind
[08:26:05] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 2067ms or 41 ticks behind
[08:27:04] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 44276ms or 885 ticks behind
but it didn't crash.
migrated
getting better, but it'd still have crashed if i hadn't upped the max ticks:
[16:43:48] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 19581ms or 391 ticks behind
migrated
pre10 still needs the max ticks set stupid high:
[08:56:44] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 20518ms or 410 ticks behind
migrated
functionally seems to be the same as:
https://bugs.mojang.com/browse/MC-132135
wobst.michael
Does it still crash in 1.13.1?
Relates to MC-132375.