Your Computer Specs and Operating System: Windows7 SP1, 32-bit dual core, 4GB ram, Java 1.6.0_26
Can you repeat this bug: yes
What issues does the bug Cause: Out of memory error with very few chunks loaded. I started a new world that we'll call World1, walked around enough to find some wood and coal, and started building a shelter. Within minutes the game was at 549MB and out of memory. I reloaded the world and the same thing happened even faster. The last verision I played was v1.6 with fairly large worlds including nether and never had memory issues on default JVM settings.
I changed JVM settings to -Xincgc -Xmx1024M and started World2. I wandered around rather than building to generate chunks. I got through about four biomes, memory usage gradually increased, and I eventually got the "invisible ground" bug. Windows showed 1080K ram in use. When I hit escape and saved the world, memory usage did NOT decrease. Reloading World1 always results in an out of memory error within a minute so that save file is corrupt. I quit MC again and started collecting wood in World2. Minecraft crashed quickly with another out of memory error at about 548K ram.
Specific conditions it occurs in if applicable: General gameplay. Building seems to trigger the issue faster, but exploration will do it.
Edit: I made a third world with the JVM set at -Xincgc -Xmx1024M and was able to stay in one area and construct a shelter for the night with no errors. It seems that the default JVM settings are not adequate, and there are file corruption issues if the JVM runs out of memory, even though the error message suggests the world will be saved.
Huh? You put on Judaism, Taosim, and Wiccanism and skipped the worlds 4th most popular religion, Buddhism? I don't think you're very qualified to be doing this sort of research.
The only thing that makes me sad is that its Xbox exclusive. I'm another console/PC hybrid gamer but my console is a PS3. I figure more money for Mojang = better minecraft overall.
That doesn't explain why it happened a second time when I quit Minecraft entirely and re-loaded the world. I only moved a few blocks, so it wouldn't have loaded enough chunks to have memory issues. Is the rendering error caused by a glitch in the save file when Minecraft has leaked itself out of memory space?
My minecraft started lagging like crazy, then crashed with an out of memory error. It's happened twice tonight, and the second time I noticed it was up to a gig of ram when I killed the JVM in Task Manager. I've never run out of memory playing Minecraft before and my usual world has a larger save file. It seems like 1.6.6 has a memory leak.
I haven't played a lot since 1.5.1 so I couldn't say which patch introduced the problem.
It happened to me as well today. My world looked exactly like CNCRaymond's screenshots. Adding fog brought the world back partly, but when I toggled through the fog settings to no fog the world was transparent again. I played for a bit with fog on, but I had the problem with blocks registered as destroyed too. I quite MC, reloaded the world, and got the transparency glitch again within a minute of loading. Memory use shot up, and I don't remember whether MC crashed that time or I quit the game. I restored a backup of the world and all was well again.
I don't know how you all make such neat branch mines. My current branch mine at layer 10 has run into two caves with lava lakes and a big cave with a 20-block high natural lavafall and a spring.
Dig up, look for coal as you go. If you run out of light and no coal, drop a furnace and make some charcoal from the wood. Just save enough for sticks.
And yeah, I understand not liking to die even if you use Invedit. I don't like skeleton archers shooting at me from the darkness whether or not I've added a couple stacks of glowstone to my inventory. LOL!
1
0
SSP or SMP: SSP
Your Computer Specs and Operating System: Windows7 SP1, 32-bit dual core, 4GB ram, Java 1.6.0_26
Can you repeat this bug: yes
What issues does the bug Cause: Out of memory error with very few chunks loaded. I started a new world that we'll call World1, walked around enough to find some wood and coal, and started building a shelter. Within minutes the game was at 549MB and out of memory. I reloaded the world and the same thing happened even faster. The last verision I played was v1.6 with fairly large worlds including nether and never had memory issues on default JVM settings.
I changed JVM settings to -Xincgc -Xmx1024M and started World2. I wandered around rather than building to generate chunks. I got through about four biomes, memory usage gradually increased, and I eventually got the "invisible ground" bug. Windows showed 1080K ram in use. When I hit escape and saved the world, memory usage did NOT decrease. Reloading World1 always results in an out of memory error within a minute so that save file is corrupt. I quit MC again and started collecting wood in World2. Minecraft crashed quickly with another out of memory error at about 548K ram.
Specific conditions it occurs in if applicable: General gameplay. Building seems to trigger the issue faster, but exploration will do it.
Edit: I made a third world with the JVM set at -Xincgc -Xmx1024M and was able to stay in one area and construct a shelter for the night with no errors. It seems that the default JVM settings are not adequate, and there are file corruption issues if the JVM runs out of memory, even though the error message suggests the world will be saved.
0
0
0
0
0
0
0
I don't think so. Mine got up to a gig and then threw an out of memory error.
0
I haven't played a lot since 1.5.1 so I couldn't say which patch introduced the problem.
0
0
0
0
0
And yeah, I understand not liking to die even if you use Invedit. I don't like skeleton archers shooting at me from the darkness whether or not I've added a couple stacks of glowstone to my inventory. LOL!