I make a world in superflat, with a layer of chests in it. it was really weird, first: chests doesn't render properly in the superflat GUI ( MC-12788 ) ok, this was alredy reported, but when the world was created, the chests were invisible, and minecraft was very laggy, especially when new chunks got generated. i messed arround with the chests, to see what minecraft do with they. sometimes chests appeared in places that doesn't have chests, and stuff like that. also, the GUI when i oppened some chest was very buggy. i make a "L" shaped triple chest, and it was looking like a double chest, with one of the chests invisible. i exit the world and reenter it, to see if minecraft render the chest in a different way, and minecraft normaly entered the loading screen, but, insted of opening the world before, it just opened the main screen, i entered the world again, and again the main screen. some seconds later, minecraft just crashed, and, when i entered the crash-reports folder, there was TWO crash reports with a -server on the name. Sorry, i'm from Brazil and my english is not perfect.
Related issues
Attachments
Comments


Duplicate of MC-1510.

always remember: chest are one thing and fire is another =3

Different block, same issue.

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.

Let me quote Grum then:
I dare to say: no bug, doing stupid shit with the generator is supposed to break you hard.

LOL, i like Grum, he is funny XD
Ok, but, if i create another issue about i fastly entering a world with the small time that the title screen appears when you'r loading a world, it will be a new issue that is not duplicated by nothing?

The crash reports you provided also duplicate MC-3766.

Yes, true. Sorry for making your busy =P

Pedro, you're referring to MC-10017.