For corrupted worlds, please see MC-2545
Crash: During the loading process of a world, Minecraft switches briefly to the main menu (see MC-185).
If you start loading a world, that takes a long time to load (due to corrupted chunks, see attached world below), when Minecraft switches to the main menu it is now possible to open a second instance of the same/another world, that will lead to the crash attached below.
Steps to reproduce:
1. Download the attached world below.
2. Start it.
3. When the game switches to the main menu quickly open the same or another world.
Minecraft crashes with the crash attached below.
Original Description:
After updating to 1.4.5, I logged in and presumed play.
At one point, an invisible (and unbreakable) block blocked my path. It was after I navigated a path around it that I noticed some serious lag.
I restarted my computer, hoping this would solve things.
Selected my save file and proceeded to load into the game
The game returned me to the main menu screen
I reselected my save file and waited during the loading screen
This is where the game crashes! Please see attached txt.
*Note
If I select my save file (the first time), and wait about 20 seconds (after being kicked back to the main menu) the game actually loads! However, it is impossible to play because of intense lag.
I have no mods installed, and I was on single player!
Basic cause: Corrupted chunks, see MC-2545.
I hope this is enough information!
Linked issues
is duplicated by 72
Attachments
Comments 36
Thanks for the reply!
Is this what you're looking for?
Seed: 51101489707484172
Spawn: 48, 64, -160
Player: 71.77, 43.0, -15.38
I'm afraid the level.dat is not enough, can you ZIP the complete world and attach here ? (only if the resulting file is smaller than 10 MB)
Seperated the crash from the world corruption. For world corruption / wrong location errors and chunk errors please see MC-2545.
Description: Sending packet
java.lang.NullPointerException
at cm.b(SourceFile:116)
at cm.a(SourceFile:41)
at jz.b(SourceFile:421)
at hm.b(SourceFile:648)
at hm.a(SourceFile:82)
at bkz.b(SourceFile:73)
at net.minecraft.server.MinecraftServer.t(SourceFile:488)
at net.minecraft.server.MinecraftServer.s(SourceFile:405)
at bkw.s(SourceFile:124)
at net.minecraft.server.MinecraftServer.run(SourceFile:339)
at hh.run(SourceFile:582)
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been deliviered.
Can you provide the seed of the world or the world itself ?