In 1.4.2(i.e latest stable update), just starting a few days ago, the game would crash upon loading up any single world, either that or it would give the OOM error message.
Here's the crash log(it seems to be the same everytime):
- Minecraft Version: 1.4.2
- Operating System: Windows Vista (x86) version 6.0
- Java Version: 1.7.0_09, Oracle Corporation
- Java VM Version: Java HotSpot(TM) Client VM (mixed mode, sharing), Oracle Corporation
- Memory: 1958264 bytes (1 MB) / 259522560 bytes (247 MB) up to 259522560 bytes (247 MB)
- JVM Flags: 0 total;
- AABB Pool Size: 292 (16352 bytes; 0 MB) allocated, 60 (3360 bytes; 0 MB) used
- Is Modded: Probably not
- Profiler Position: N/A (disabled)
- Vec3 Pool Size: 64 (3584 bytes; 0 MB) allocated, 64 (3584 bytes; 0 MB) used
- Player Count: 1 / 8; [ih['aloy99'/22, l='Waking Up', x=95.50, y=54.00, z=-0.50]]
- World Waking Up Entities: 2 total; [ih['aloy99'/22, l='Waking Up', x=95.50, y=54.00, z=-0.50], lq['Painting'/24, l='Waking Up', x=101.94, y=53.50, z=-4.00]]
- World Waking Up Players: 1 total; [ih['aloy99'/22, l='Waking Up', x=95.50, y=54.00, z=-0.50]]
- World Waking Up Chunk Stats: ServerChunkCache: 441 Drop: 0
- Type: Integrated Server
java.lang.OutOfMemoryError: Java heap space
at dj.a(SourceFile:183)
at dl.<init>(SourceFile:41)
at ih.j_(SourceFile:147)
at xe.a(SourceFile:1218)
at ie.a(SourceFile:424)
at xe.g(SourceFile:1197)
at xe.h(SourceFile:1122)
at ie.h(SourceFile:352)
at net.minecraft.server.MinecraftServer.r(SourceFile:718)
at net.minecraft.server.MinecraftServer.q(SourceFile:661)
at bcb.q(SourceFile:117)
at net.minecraft.server.MinecraftServer.run(SourceFile:595)
at fp.run(SourceFile:818)
--- END ERROR REPORT 4c92a4b8 ----------
I do know that running minecraft with more memory should solve this, but it happened all of a sudden for no apparent reason. My computer was also having some hiccups though, such as HL2.exe refusing to launch or just general lag and BSODs(reason for which was memory_management). However, when I get around to making a .bat file upon logging in it stays at Logging In and never does actually launch the game.
Are there any non-hardware related fixes for the above issues?
Thanks
You should do the basic check when a computer BSOD's windows registry is corrupt, Virus or spyware. Allowing minecraft to use more memory slows it down as well i seen a number of reports about this on forums. If you are getting a memory error (Ram) you can always do a memory check as well. Looks like you need to update java as well.
Here's the crash log(it seems to be the same everytime):
I do know that running minecraft with more memory should solve this, but it happened all of a sudden for no apparent reason. My computer was also having some hiccups though, such as HL2.exe refusing to launch or just general lag and BSODs(reason for which was memory_management). However, when I get around to making a .bat file upon logging in it stays at Logging In and never does actually launch the game.
Are there any non-hardware related fixes for the above issues?
Thanks
-
View User Profile
-
View Posts
-
Send Message
Retired StaffOdd