The game crashed after teleporting to a location and then flying around in spectator. The full crash report is attached.
While searching for a duplicate, I came across MC-134762, but that appears to be a client crash.
1.14 Pre-Release 5\: [^crash-2019-04-20_01.07.58-server.txt]
---- Minecraft Crash Report ----
// Oops.
Time: 4/20/19 1:07 AM
Description: Exception ticking world
java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901)
at java.util.ArrayList$Itr.next(ArrayList.java:851)
at bhu.a(SourceFile:72)
at vg.a(SourceFile:317)
at net.minecraft.server.MinecraftServer.b(SourceFile:827)
at net.minecraft.server.MinecraftServer.a(SourceFile:764)
at dxh.a(SourceFile:128)
at net.minecraft.server.MinecraftServer.run(SourceFile:632)
at java.lang.Thread.run(Thread.java:745)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Thread: Server thread
Stacktrace:
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901)
at java.util.ArrayList$Itr.next(ArrayList.java:851)
at bhu.a(SourceFile:72)
at vg.a(SourceFile:317)
-- Affected level --
Details:
Level name: Gamemode4Dev 1.14
All players: 1 total; [vh['misode'/256735, l='Gamemode4Dev 1.14', x=1560.98, y=77.48, z=-917.10]]
Chunk stats: ServerChunkCache: 4153
Level seed: 4922589396274518660
Level generator: ID 00 - default, ver 1. Features enabled: true
Level generator options: {}
Level spawn location: World: (-192,73,-64), Chunk: (at 0,4,0 in -12,-4; contains blocks -192,0,-64 to -177,255,-49), Region: (-1,-1; contains chunks -32,-32 to -1,-1, blocks -512,0,-512 to -1,255,-1)
Level time: 996930 game time, 1244 day time
Level dimension: 0
Level storage version: 0x04ABD - Anvil
Level weather: Rain time: 1 (now: false), thunder time: 1 (now: false)
Level game mode: Game mode: creative (ID 1). Hardcore: false. Cheats: true
Stacktrace:
at net.minecraft.server.MinecraftServer.b(SourceFile:827)
at net.minecraft.server.MinecraftServer.a(SourceFile:764)
at dxh.a(SourceFile:128)
at net.minecraft.server.MinecraftServer.run(SourceFile:632)
at java.lang.Thread.run(Thread.java:745)
-- System Details --
Details:
Minecraft Version: 1.14 Pre-Release 5
Operating System: Windows 10 (amd64) version 10.0
Java Version: 1.8.0_51, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 1253340424 bytes (1195 MB) / 2147483648 bytes (2048 MB) up to 2147483648 bytes (2048 MB)
JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M
Player Count: 1 / 8; [vh['misode'/256735, l='Gamemode4Dev 1.14', x=1560.98, y=77.48, z=-917.10]]
Data Packs: vanilla, file/base (incompatible), file/gm4_orbis (incompatible), file/gm4_cooler_caves (incompatible), file/gm4_dangerous_dungeons (incompatible), file/gm4_tower_structures (incompatible)
Type: Integrated Server (map_client.txt)
Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.Related issues
is duplicated by
Attachments
Comments
migrated
migrated
spreadplayers also crashes the server with the same exception.
md_5
Can be reasonably reliably reproduced by just generating a few thousand chunks.
A ticking fluid checks if adjacent chunks are loaded, but for some reason the method that checks if the chunks are loaded ends up actually loading part of the chunk, which causes more things to be marked for ticking --> crash.
migrated
Same error happened to us today, had 6 people on the server. New terrain being generated, definitely lots of chunks being loaded for multiple people, boom. 😞
migrated
Happens Constantly with our server- But specifically when loading ocean chunks. I had my server crash, 5 times within an hour :/
migrated
I had 2 consecutive crashes while flying in a single player survival no cheats world. The world was created after 1.14 release. As md_5 describes. It was while flying in a straight line, loading many new chunks. Render distance: 17
Update* On 3rd reload was able to land and let the chunks load. Maybe relevant, but similar to Morgan Bonds, I was over a large body of water.
migrated
Can confirm this happens if you turn off the elytra check. When elytra check is turned off, flying too fast can cause the same crash.
migrated
having the same issue as well
migrated
I can confirm that the steps to recreate this issue works as md_5 has stated, having the same issue as well. During more busy periods when a lot of new chunks are getting created the server will crash, especially when players are playing around with Elytra, I've tested this multiple times and I get the exact error, tested on 1.14.
migrated
This bug happens with my server with 6-10 players logged on fairly regularly, and it sometimes takes less than an hour. There are no new chunks being generated, however part of the world was generated in a Pre-Release. Noone has elytra yet, they're all just loading chunks I've already generated by foot or by boat.
According to what my players have said, I think the oceans might magnify the problem. The server had already crashed before; after I restarted it, I was in the ocean with one of my players (although there were others throughout the world), and the lag just kept increasing until I manually restarted the server. While I was offline, the lag returned and eventually led to this crash.
I have three data packs installed other than vanilla}}–two use the {{schedule command to tick, one uses a repeating command block in each dimension (loaded with forceload), and (as a temporary solution to a minor issue I encountered) they all hook into player damage through the advancement trigger minecraft:entity_hurt_player. Additionally there is a shared function that use schedule.
Attached is the result of a short profiling of the server during the excessive lag leading up to the crash described in this bug. Notably, 70.20% of overall ticking occurred in tick.levels.world minecraft:overworld.tick.tickPending.ticking.unspecified. I will attempt to get a profile over a longer span of time during the excessive lag.
migrated
With 20-30 players online I crash anywhere from 1 minute up to about 1 hour at the longest. Using spread players with 20 or more players online will almost instantly crash the server. Players using boats appears to at lease triple the frequency of the crashes. The server will also hang without crashing sometimes, not sure if this is a related issue.
Tez1010
simply placing a block in creative with one person on my server (me) in already loaded chunks got the stack overflow error
mrfloris
We can reproduce this on linux distros, macOS and Windows OS. It prevents us from --forceUpgrade and pre-generating chunks and upgrading.
Hopefully 1.14.1 will address this
migrated
My similar crash was probably not due to heavy RAM load or too many players.
The crash happened this morning (2019-04-29) and threw "Exception ticking world" with an identical stack trace.
There was 1 player on my virtual private server which is running Minecraft 1.14 with 4 Gigs of RAM.
The world was freshly created yesterday. The player had only loaded a few hundred chucks in a straight path away from spawn.
I don't know the CPU load, so that is a possibility.
My VPS shares a quad core Intel Xeon E3-1270 running at 3.5 Ghz with other private servers at my hosting provider.
Disk latency could also be the problem.
However, I don't have hard drive transfer rate specks or issue logs.
migrated
I don't think this was fixed, I still get this issue on pre 1.
Misode
boq