Put the summary of the bug you're having here
What I expected to happen was...:
Describe what you thought should happen here
I was riding an armored horse to a desert outpost, mapping already generated and explored territory. The map I was using was linked to a map in a map room.
What actually happened was...:
Describe what happened here
The game crashed.
Steps to Reproduce:
Not really sure. I've noticed choppy behavior when forcing the game to generate new terrain (i.e. traveling to ungenerated chunks), but for the most part travel in terrain generated prior to upgrading to 1.8 has been smooth. This was choppy for some reason.
Now for the big weirdness! My world was deleted. Fortunately I saved it off somewhere.
1. Put a step by step guide on how to trigger the bug here
2. ...
3. ...
Linked issues
is duplicated by 1
Attachments
Comments 4
java.lang.OutOfMemoryError: Tesselating block model
Operating System: Windows 7 (x86) version 6.1
JVM Flags: 7 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -Xms1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn256M
Out of memory. while rendering.
Reduce the chunk render distance. You cannot have high render distances with a 32 bit OS. Think about upgrading to 64 bit.
Good heavens, I've been playing this off and on for a year and I never noticed it was using the x86 Java. I'm installing the x64 Java and will change my MC launcher to use it (Windows itself is already x64, inspite of what the environment states). Thank you for spotting that obvious blunder!
Crash report.