Mod note
This issue is about crashing in normal / amplified / customized worlds when updating water and/or lava.
Issues about crashing in superflat worlds with blocks needing a support layer is MC-93162
I was in Survival with cheats on (gamemode 1 at time of crash) and I was teleporting to possible village locations that AMIDST-3.3 had shown on its map of seed #1, default biomes. I was at 4656, 80, 4320 and was trying to teleport to 2576, 80, 4336 and I crashed when Minecraft tried to load the terrain. A 2nd attempt resulted in the same crash. The 3rd time I tried to fly there and when I was near the possible village I saw a savanna plateau just before I crashed. I had seen in another savanna an area where the plateau had gone past the clouds and a floating island way past cloud level but not where it would break the height limit. I don't have a screen shot of the area where I crashed but I have one of the other savanna plateau with the island that went past the clouds
Additionally here is something of value I found in the launcher that's not in the crash reports
Client> 2013-09-21 12:25:13 [SERVER] [INFO] Saving and pausing game...
Client> 2013-09-21 12:25:13 [SERVER] [INFO] Saving chunks for level 'Seed no1'/Overworld
Client> 2013-09-21 12:25:13 [SERVER] [INFO] Saving chunks for level 'Seed no1'/Nether
Client> 2013-09-21 12:25:13 [SERVER] [INFO] Saving chunks for level 'Seed no1'/The End
Client> 2013-09-21 12:26:00 [SERVER] [WARNING] Can't keep up! Did the system time change, or is the server overloaded?
Client> 2013-09-21 12:26:47 [SERVER] [WARNING] Can't keep up! Did the system time change, or is the server overloaded?
Client> Warning: Clientside chunk ticking took 104 ms
Client> Warning: Clientside chunk ticking took 261 ms
Client> Warning: Clientside chunk ticking took 185 ms
Client> 2013-09-21 12:27:31 [SERVER] [WARNING] Can't keep up! Did the system time change, or is the server overloaded?
Client> 2013-09-21 12:28:18 [SERVER] [WARNING] Can't keep up! Did the system time change, or is the server overloaded?
Client> Warning: Clientside chunk ticking took 147 ms
Client> Warning: Clientside chunk ticking took 152 ms
Client> Warning: Clientside chunk ticking took 195 ms
Client> Warning: Clientside chunk ticking took 206 ms
Client> s: Exception while updating neighboursHow to reproduce
From MC-104804
Amplified generation with the following seed
6455076524068966402Debugging info
[media] includes the method calls for an amplified world with the seed 6455076524068966402 before the crash. Format is:
X Y Z ACTION/METHOD BLOCK_ID LEVELwhere BLOCK TICK as ACTION is when the world generation updates a block after it placed it. Therefor the actions after the last BLOCK TICK are the interesting ones.
All updates are immediately during generation (net.minecraft.world.World.immediateBlockTick(BlockPos, IBlockState, Random)), so in general changing this to have them be scheduled might solve this problem.
Linked issues
is duplicated by 60
MC-35355
Hopper: java.lang.StackOverflowError: Exception while updating neighbours
Resolved
MC-29583
Hopper: java.lang.StackOverflowError
Resolved
MC-29612
Hopper: java.lang.StackOverflowError
Resolved
MC-29694
Hopper: java.lang.StackOverflowError
Resolved
MC-29755
Hopper: java.lang.StackOverflowError
Resolved
relates to 4
MC-93162
Exception while updating neighbours java.lang.StackOverflowError (blocks needing a support block)
Resolved
MC-108660
Loading a specific structure containing observers and piston with stucture block crashes server
Resolved
MC-111118
Crash: java.lang.StackOverflowError: Exception while updating neighbours
Resolved
MC-118839
A certain Woodland Mansion always crash with StackOverflowError and get "cut" when the game has only 512 MB RAM available
Resolved
Attachments
Comments 23
As I said Anon,
the seed is 1, Default Biomes, not amplified,
I was at 4656, 80, 4320 (I had expected a village but got a witch hut instead)
and I was trying to teleport to 2576, 80, 4336 (the location of another possible village)
When I teleported there, I crashed instantly before the chunks loaded. When I flew there I was able to see briefly what I thought was a floating island similar to what is in the screen shot but I crashed again before I got to the village. I tried this on the 13w37b snapshot and crashed again.
I'm clueless as to what's causing this. I do not use mods of any kind.
Snippet from crash report
Description: Exception while updating neighbours
java.lang.StackOverflowError
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$100(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at ade.e(SourceFile:467)
at ade.d(SourceFile:445)
at aqr.a(SourceFile:74)
at kn.a(SourceFile:312)I'm getting this exact same problem, but I'm having an issue with sand. The symptoms are the exact same thing.
I used the farlands mod to generate the terrain it happened in, but I didn't see the class file it modified in the stack trace. I then loaded the world in unmodded vanilla minecraft and got the same result. It was a custom world generated with a custom worldgen, but the world still crashed when loaded without the mods.
EDIT: So in plain vanilla minecraft, used -Xss8M to increase the stack size, then I teleported to one of the sand blocks in question. I saw a floating cactus in the air a couple blocks from the line of crashing sand blocks. It seemed odd to have a cactus floating in midair, and I wonder if that may have anything to do with it.
I'm not gonna go into the technical details – as I can clearly see, many others have had the same problem. With me it was saplings. I lost about a week of progress, I don't know how to fix it, and this is obviously still an issue in 1.12.2. I hope this gets fixed in 1.13, but given that the first report is from 1.7, my hopes are not high. This is a CONFIRMED bug with serious consequences, so why hasn't it been fixed?
Please have the people at Mojang take a look at this bug and for the time being, please tell me how I can restore my progress.
Very similar crash, however this was on 1.14 .. Crash log @ https://pastebin.com/fbn2pyYi
Please attach seed and coordinates. Are you in an amplified world?