When a Firework is spawned either with summon command, from a dispenser or by placing it on ground and if the player dies immediately after. If you stay on the death screen for a while, the client freezes. Sometimes it recovers and you don't have to restart MC. The problem is worse the longer you stay on the death screen. If you click Respawn straight away, then everything is usually ok.
To reproduce this bug make the following redstone machine:
1, place pressure plate on ground
2, place command block with command "kill @p"
3, On the other side of pressure plate put a command block with firework summon command such as:
/summon FireworksRocketEntity ~ ~ ~ {LifeTime:20,Motion:[0.00,0.00,0.10],FireworksItem:{id:401,Count:1,tag:{Fireworks:{Explosions:[{Type:1,Flicker:0,Trail:1,Colors:[2293504,10895615],FadeColors:[16777215]},{Type:4,Flicker:0,Trail:1,Colors:[16716820],FadeColors:[16777215]},{Type:1,Flicker:0,Trail:1,Colors:[2959103],FadeColors:[16777215]},{Type:4,Flicker:0,Trail:1,Colors:[16713942],FadeColors:[16777215]}]}}}}Now do the following:
1.Stand on pressure plate
2.When you die, wait on the Respawn screen for more than 10 seconds.
3.Now click Respawn. The client will probably hang for a while or freeze completely.
This bug is worse when playing on a server but seems to still happen in single player but not as bad(client more likely to recover).
Linked issues
relates to
Attachments
Comments
kumasasa
The output of the dev console. And a screen shot of the Window showing that MC is "Not Responding"
This is the console log after I quit out. It has a bit more information at the bottom.
kumasasa
Cannot confirm the termination of the game with
[22:10:41 ERROR]: Game ended with bad state (exit code 1073807364)but with
[23:40:38 INFO]: Client> [23:40:38] [Client thread/INFO]: [CHAT] [@: Object successfully summoned]
[23:40:38 INFO]: Client> [23:40:38] [Client thread/INFO]: [CHAT] Kumasasa fell out of the world
[23:40:38 INFO]: Client> [23:40:38] [Client thread/INFO]: [CHAT] [@: Killed Kumasasa]
[23:40:56 INFO]: Client> [23:40:56] [Client thread/INFO]: [CHAT] Saved screenshot as 2014-02-17_23.40.56.png
[23:43:31 ERROR]: Game ended with bad state (exit code -805306369)which means "out of memory"
marcono1234
Confirmed for
14w30c It doesn't crash for me but creates lag for about 5 seconds after the 10 seconds of waiting
14w31a
Minecraft 1.8-pre 1
marcono1234
marcono1234
Relates to MC-5120 and please format the command in the description
wobst.michael
Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w42a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.
After having this issue:
Please attach the complete output of the "Development console" which can be found on the second tab of the launcher.
If the launcher closes after game start, please edit your profile and select "Launcher visibility" then, "Keep the launcher open".