[MC-30887] setblock Locked Chest (or ID 95) Crashes Minecraft when spawned at ~ ~1 ~

I was testing with the /setblock command and when I pressed tab I noticed that the locked chest was listed. I spawned it, but the game crashed. This also rendered my world impossible to open before removing the locked chest with a 3rd party program.

Linked issues

duplicates 1

MC-12984 getting a locked chest pushed into your head crashes the game Resolved

Attachments

crash-2013-09-12_23.12.17-client.txt

crash-2013-09-12_23.14.22-client.txt

Comments 6

kumasasa 2013-09-12T21:14:55Z

Can confirm crash with /setblock ~ ~1 ~ 95.
When issuing /setblock ~ ~ ~ 95 the block gets placed, see attachment.

WolfieMario 2013-09-14T12:13:41Z

This is not a duplicate of MC-12984. MC-12984 happens when your head is inside a locked chest, because the game incorrectly tries loading its nonexistent texture for the suffocation overlay.

This bug occurs without the need to ever shove the thing on your head - it happens when spawning the block with /setblock. I think this should be reopened.

kumasasa 2013-09-14T12:25:04Z

No, the block is placeable without crash, see recent screenshots.
It crashes only if the block is spawned at ~ ~1 ~.

MC-12984

Description: Unexpected error
java.lang.NullPointerException
	at bde.a(SourceFile:501)
	at bde.b(SourceFile:462)
	at bcz.b(SourceFile:463)
	at bcz.a(SourceFile:923)

This

Description: Unexpected error
java.lang.NullPointerException
	at bic.a(SourceFile:509)
	at bic.b(SourceFile:467)
	at bhx.b(SourceFile:476)
	at bhx.a(SourceFile:939)

WolfieMario 2013-09-14T12:50:22Z

Ah, that's clever. Sorry, I didn't think OP was spawning it inside their head.

kumasasa 2013-09-14T12:55:48Z

Don't know if OP did that deliberately or accidently, but that was (at least for me) the only way to trigger the crash...
But, you wrote:

This bug occurs without the need to ever shove the thing on your head - it happens when spawning the block with /setblock. I think this should be reopened.

Can you provide a command to trigger that crash with other parameters as ~ ~1 ~ ?

WolfieMario 2013-09-22T20:19:25Z

Sorry, you're right. I made the mistake of assuming OP didn't do ~ ~1 ~ because he didn't say he did ~ ~1 ~. I'll check by myself in the future before making stupid/unbased claims.