Custom superflat world crashes when certain block type is chosen
I tried to make a superflat world, where the custom preset is set to only generate one layer of fire. After generating and loading the world, the client crashed, and this is the crashlog:
*****
---- Minecraft Crash Report ---- // Hey, that tickles! Hehehe! Time: 31-10-12 20:00 Description: Exception in server tick loop java.lang.StackOverflowError at zb.b(SourceFile:73) at za.c(SourceFile:332) at za.a(SourceFile:351) at za.a(SourceFile:338) at xe.b(SourceFile:296) at xe.e(SourceFile:343) at aiu.a(SourceFile:249) at xe.m(SourceFile:419) at xe.h(SourceFile:408) at xe.f(SourceFile:365) at xe.e(SourceFile:344) at aiu.a(SourceFile:249) ... and so on. Relevant Details: - Minecraft Version: 1.4.2 - Operating System: Windows 7 (amd64) version 6.1 - Java Version: 1.7.0_07, Oracle Corporation - Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation - Memory: 327751592 bytes (312 MB) / 681705472 bytes (650 MB) up to 954466304 bytes (910 MB) - JVM Flags: 2 total; -Xms512m -Xmx1024m - AABB Pool Size: 11 (616 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used - Is Modded: Probably not - Profiler Position: N/A (disabled) - Vec3 Pool Size: 1 (56 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used - Player Count: 1 / 8; [ih['zenyl'/0, l='Test', x=-379,50, y=0,62, z=-731,50]] - World Test Entities: 0 total; [] - World Test Players: 0 total; [] - World Test Chunk Stats: ServerChunkCache: 0 Drop: 0 - Type: Integrated Server *****
What I expected to happen was that the client would crash, which is what I got.
What actually happened was that the client crashed
Describe what happened here
Steps to Reproduce:
1. Make a custom preset for a superflat world, but only with 1 layer, of fire (51).
2. Let it load (takes some time)
3. Client crash.
This is, of course, a minor bug, but since you guys asked for bugs... ![]()
Environment
Put your operating system (Windows 7, Windows XP, OSX) and Java version if you know it here
Linked Issues
is duplicated by59
relates to4
Created Issue:
Superflat crashes if only fire is chosen
I tried to make a superflat world, where the custom preset is set to only generate one layer of fire. After generating and loading the world, the client crashed, and this is the crashlog:
*****
---- Minecraft Crash Report ----
// Hey, that tickles! Hehehe!Time: 31-10-12 20:00
Description: Exception in server tick loopjava.lang.StackOverflowError
at zb.b(SourceFile:73)
at za.c(SourceFile:332)
at za.a(SourceFile:351)
at za.a(SourceFile:338)
at xe.b(SourceFile:296)
at xe.e(SourceFile:343)
at aiu.a(SourceFile:249)
at xe.m(SourceFile:419)
at xe.h(SourceFile:408)
at xe.f(SourceFile:365)
at xe.e(SourceFile:344)
at aiu.a(SourceFile:249)
... and so on.Relevant Details:
- Minecraft Version: 1.4.2
- Operating System: Windows 7 (amd64) version 6.1
- Java Version: 1.7.0_07, Oracle Corporation
- Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
- Memory: 327751592 bytes (312 MB) / 681705472 bytes (650 MB) up to 954466304 bytes (910 MB)
- JVM Flags: 2 total; -Xms512m -Xmx1024m
- AABB Pool Size: 11 (616 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
- Is Modded: Probably not
- Profiler Position: N/A (disabled)
- Vec3 Pool Size: 1 (56 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
- Player Count: 1 / 8; [ih['zenyl'/0, l='Test', x=-379,50, y=0,62, z=-731,50]]
- World Test Entities: 0 total; []
- World Test Players: 0 total; []
- World Test Chunk Stats: ServerChunkCache: 0 Drop: 0
- Type: Integrated Server
*****What I expected to happen was that the client would crash, which is what I got.
What actually happened was that the client crashed
Describe what happened hereSteps to Reproduce:
1. Make a custom preset for a superflat world, but only with 1 layer, of fire (51).
2. Let it load (takes some time)
3. Client crash.This is, of course, a minor bug, but since you guys asked for bugs...
Environment
Put your operating system (Windows 7, Windows XP, OSX) and Java version if you know it here
Linked Issues
is duplicated by3
TRASH-24108
TRASH-499
TRASH-497
I tried to make a superflat world, where the custom preset is set to only generate one layer of fire. After generating and loading the world, the client crashed, and this is the crashlog:
*****
---- Minecraft Crash Report ----
// Hey, that tickles! Hehehe!Time: 31-10-12 20:00
Description: Exception in server tick loopjava.lang.StackOverflowError
at zb.b(SourceFile:73)
at za.c(SourceFile:332)
at za.a(SourceFile:351)
at za.a(SourceFile:338)
at xe.b(SourceFile:296)
at xe.e(SourceFile:343)
at aiu.a(SourceFile:249)
at xe.m(SourceFile:419)
at xe.h(SourceFile:408)
at xe.f(SourceFile:365)
at xe.e(SourceFile:344)
at aiu.a(SourceFile:249)
... and so on.Relevant Details:
- Minecraft Version: 1.4.2
- Operating System: Windows 7 (amd64) version 6.1
- Java Version: 1.7.0_07, Oracle Corporation
- Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
- Memory: 327751592 bytes (312 MB) / 681705472 bytes (650 MB) up to 954466304 bytes (910 MB)
- JVM Flags: 2 total; -Xms512m -Xmx1024m
- AABB Pool Size: 11 (616 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
- Is Modded: Probably not
- Profiler Position: N/A (disabled)
- Vec3 Pool Size: 1 (56 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
- Player Count: 1 / 8; [ih['zenyl'/0, l='Test', x=-379,50, y=0,62, z=-731,50]]
- World Test Entities: 0 total; []
- World Test Players: 0 total; []
- World Test Chunk Stats: ServerChunkCache: 0 Drop: 0
- Type: Integrated Server
*****What I expected to happen was that the client would crash, which is what I got.
What actually happened was that the client crashed
Describe what happened hereSteps to Reproduce:
1. Make a custom preset for a superflat world, but only with 1 layer, of fire (51).
2. Let it load (takes some time)
3. Client crash.This is, of course, a minor bug, but since you guys asked for bugs...
I tried to make a superflat world, where the custom preset is set to only generate one layer of fire. After generating and loading the world, the client crashed, and this is the crashlog:
*****
---- Minecraft Crash Report ---- // Hey, that tickles! Hehehe! Time: 31-10-12 20:00 Description: Exception in server tick loop java.lang.StackOverflowError at zb.b(SourceFile:73) at za.c(SourceFile:332) at za.a(SourceFile:351) at za.a(SourceFile:338) at xe.b(SourceFile:296) at xe.e(SourceFile:343) at aiu.a(SourceFile:249) at xe.m(SourceFile:419) at xe.h(SourceFile:408) at xe.f(SourceFile:365) at xe.e(SourceFile:344) at aiu.a(SourceFile:249) ... and so on. Relevant Details: - Minecraft Version: 1.4.2 - Operating System: Windows 7 (amd64) version 6.1 - Java Version: 1.7.0_07, Oracle Corporation - Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation - Memory: 327751592 bytes (312 MB) / 681705472 bytes (650 MB) up to 954466304 bytes (910 MB) - JVM Flags: 2 total; -Xms512m -Xmx1024m - AABB Pool Size: 11 (616 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used - Is Modded: Probably not - Profiler Position: N/A (disabled) - Vec3 Pool Size: 1 (56 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used - Player Count: 1 / 8; [ih['zenyl'/0, l='Test', x=-379,50, y=0,62, z=-731,50]] - World Test Entities: 0 total; [] - World Test Players: 0 total; [] - World Test Chunk Stats: ServerChunkCache: 0 Drop: 0 - Type: Integrated Server *****What I expected to happen was that the client would crash, which is what I got.
What actually happened was that the client crashed
Describe what happened hereSteps to Reproduce:
1. Make a custom preset for a superflat world, but only with 1 layer, of fire (51).
2. Let it load (takes some time)
3. Client crash.This is, of course, a minor bug, but since you guys asked for bugs...
relates to
is duplicated by
duplicates
is duplicated by
duplicates
is duplicated by
relates to
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
relates to
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
Superflat crashesif only fire is chosenCustom superflat world crashes when certain block type is chosen
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
MC-42198
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Sorry, misread your comment...
is duplicated by
is duplicated by
TRASH-24108
is duplicated by
is duplicated by
is duplicated by
relates to
Duplicate of MC-1510 , please use the search function to see if your bug has already been submitted. Currently over 30% of tickets are being closed as duplicate.
How is this duplicate of MC-1510 ?? It's completely different bug!
Duplicate of MC-1510, please use the search function to see if your bug has already been submitted. Currently over 51% of tickets are being closed as duplicate.
Duplicate of MC-1510, please use the search function to see if your bug has already been submitted. Currently over 53% of tickets are being closed as duplicate.
Duplicate of MC-1510. Please use the search function to check before posting in the future.
my crashes are server side, the crash of MC-1510 is client side, his crsh was generated when he created the world, my crash was generated before triyng openning the world for the second time. my report is not about the crash, i think the crash is another issue for lag computers and oppening world goes to the title screen for a sec, but, in laggy computers you have enought time to interact eith the title screen. (i don't know, i can't code java things =P) anyway, they are different issues.
Block 36 is a technical block used by pistons. It's not intended to be used for anything else. Any other use of it would be a bug. They may not have fixed it deliberately; it may just be a casualty of fixing some other bug.
Crashing is something they should fix – though they've said in the past that the game crashing when you do something you're not supposed to do (ex MC-1510, MC-31447) is intentional, desirable, or not worth fixing.
Duplicate of MC-1510
Making a world entirely made of sign blocks is not useful. Don't do stupid things with the generator and you wont crash.
Duplicate of Unresolved
MC-1510
If you have not, please use the search function in the future, to see if your bug has already been submitted. If you could not find the original report, please comment with the keywords you searched for.
Thank you for your report!
We're tracking this issue in MC-1510, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automagically! Please report any issues in Discord or Reddit
Duplicate of MC-1510, this will not be fixed.
Related Tickets: MC-15975, MC-1510
Summary:
When I breaking bed in Bed Flat, this world and game will be crash even affected in Java Edition on this related tickets.
Step to reproduce:
- Extract this zip files to minecraftWorlds
- Open this game
- Open this world
- Read the book, you can see this book step to reproduce.
- Follow the instructions from the book Step to reproduce.
Observed Results:
This game and world will be crash
Expected Results:
I dont know this should game will not to crash, but will should be changed to Disconnected due world corruption.
Thank you for your report!
We're tracking this issue as MC-1510, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Won't Fix, which means this is considered a bug but won't be fixed. The description of that ticket or the comments might explain the rationale. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Also happens with redstone dust/wire and comparators (might not be the exact same issue). But isn't this a duplicate of MC-1510?
Confirmed. The crash dump winds up with the following chunk of text being repeated over and over:
at aiu.a(SourceFile:249)
at xe.m(SourceFile:419)
at xe.h(SourceFile:408)
at xe.f(SourceFile:365)
at xe.e(SourceFile:344)
(Insert witty comment about watching the world burn here)
I dare to say: no bug, doing stupid shit with the generator is supposed to break you hard.
After all, we are stress-testing Minecraft.
1 fire disappears, updates fire blocks next to it, they also disappear, update blocks next to them... This repeats infinitely. This is supposed to happen. The bug is that it would take infinite time to do this, so it crashes. It'd be pretty difficult (if possible at all) to change infinite number of blocks in a finite time, and it wouldn't be ever used by sane players, so I agree with Grum.
I strongly disagree that this is not a bug - the client should never crash, it should always handle user errors gracefully
In this case, making sure that selected blocks in the menu are not all transparent would suffice, i'd have thought
According to you, LordAro, the game should not crash even if you make it do impossible stuff.
That's like saying a car should still work after you total it. It's not going to happen.
User error is not a valid bug. Grum is right.
obviously it shouldn't work. but a program shouldn't allow users to do stupid stuff. programs are made for stupid users. (no offense
)
all it needs is an error message before (instead of) world generation that says "bohoo! sorry, you can't do that!"
This bug is no longer just about one layer of fire. My bug was marked as a duplicate of it (6432), which involved creating a super-flat that had a layer of tripwires. I was trying to see if zombie pigmen would spawn on (really in) tripwires. The easiest way for me to check was to create a superflat world with a layer of tripwires and set the biome to 8 (Nether).
I did the same thing for half-slabs and pressure plates (no spawns on either of those).
It may not be possible to have a real world with just fire, but I could certainly have a real world with many, many tripwires. I would hope that would work.
@Xavier I'd say it's more like a car exploding if you tilt the seat too far forward and turn the steering wheel to the left while the parking brake is on. It would be terrible if your entire web browser crashed because you put a "~" between the "http" and the "://" or executed an infinite loop in some javascript somewhere.
Errors that can be handled gracefully should be, preferably returning the game to a functioning state, even if that's just the main menu or a screen with a button to get there.
That isn't nearly as bad as overloading it with impossible stuff.
How is
MC-1283duplicate of this??? It's completely different bug!you would need mods to do that soi dont think that would be of that much concern.
@Brad: You do not need any mods to reproduce this bug. All you need to do is make a custom, superflat world.
I had the same problem. But with "Snow" (Decoration) as the only layer. Destroyed one "Snow" & the game crashed. No error report came up (I don't think). Went back on & there was a chunk of 1 line missing, starting from where I hit it.
P.S: Where do the error reports appear?
@Daniel
On windows, type windows key + r to open run, then type %appdata%
Open .minecraft
Open crash-reports
The most recent one should be on the bottom.
On other operating systems, run may not exist, but appdata still does.
%appdata% is Windows only. On Linux minecraft's save location is
and on Mac it's
Or you can just follow this link:
file:///%appdata%/.minecraft/crash-reports/
(For some reason, this may not work, just copy it into the browserbar then)
Well, I am pretty sure "%appdata%" is a global link that's used on all operating systems, not 100% sure though.
Damn, who uses recursion in worldgen? Who taught (whoever wrote superflat worldgen) programming? This is shitcode, not a simple bug.
If I recall the actual cause of this bug (which I last tested, oh, 6 years ago back when I knew a lot less (just look at that appdata comment...)), it's not during the world generation, but instead once the world finishes loading and things start ticking. Because when you update one of the fire blocks (or the fire block receives a random update; if you use e.g. ladders then it'll only break when updated manually), it'll update its neighbors, and then those neighbors update their neighbors, for all of them. And since all of the fire blocks are in an invalid state, they all self-destruct, and there's no end to the updating. Now, it could be implemented without recursion by queuing in a list, but there still are far too many blocks for it to finish quickly and it's probably better for it to just crash that way.
Affecting Bedrock Edition. Relates
MCPE-115009and closed as Invalid, I modifying nbt and play with bed flat. When I breaking many beds in infinite beds, the game will crash.