I made a bug report, and was told that it was linked to this one. I'll try to fix it.
Just a quick note that this works on the default world type aswell. I'm on amplified, but it works on all world types.
I put up the crash report now. First time I ever had to force a crash.
You should be able to reproduce the glitch easily anyway.
There's no crash involved.
Ok, now I know. Thanks!
I have to say, I didn't know that.
Confirmed for 1.9pre4.
The new sounds are asset changes, so this issue can be supported. Perhaps you should post this issue onto the Minecraft Launcher issue tracker.
They couldn't add regular chests as a placeholder? Wow, Mojang, Wow!
And I think the invisible chests bug was fixed.
But they could have just put in regular chests as a placeholder, like how abandoned mineshafts generated normal chests before 1.5.
And also, stronghold storage rooms share the same bug. You can see for yourself that they are missing, by using a seed like "robot".
Also, there is a similar issue where end stone bricks are as weak as sandstone (blast resistance 4), yet regular end stone is a lot stronger (blast resistance 45).
I think this is still in 16w03a.
The only valid reason is that it would be possible for mining the floor of dungeons. to lead into the void.
And no, it's on any world. I put a steps to reproduce section, because it would be very hard to prove that they don't cut through the second last layer with screenshots. All I'm saying is that the reason for underground structures to not cut through the second last layer is unknown to everyone but Mojang. For example, have you ever seen an abandoned mineshaft cut through the second last layer but not the last? Well, it's obvious it shouldn't cut through the bottom layer or the void would be accessible.
No, I meant they should go down to the layer that only has bedrock, the second last layer has some stone.
This might also apply to caves in The Nether.
Come on! It's still in 1.8-pre2 and it's probably never going to be fixed. Come on, Mojang, see and fix this before 1.8 is fully released, otherwise, it will be in it!
The big reason I'm doing this, like I said before, is because I want this fixed before 1.8 comes out. And I remember that 1.7.2 was buggy enough.
Turned VBOs on. I'm gonna keep it on for now, because it fixed the issue for me.