Minecraft Forums

Hi, whenever I try to play the latest snapshot, (which is 13w47c) it crashes with this
:---- Minecraft Crash Report ----// Daisy, daisy...Time: 5/9/13 3:42
PMDescription: Updating screen eventsjava.lang.OutOfMemoryError: unable to create new native threadat java.lang.Thread.start0(Native Method)at java.lang.Thread.start(Unknown Source)at bkf.(SourceFile:110)at axk.a(SourceFile:20)at axr.a(SourceFile:72)at axr.d(SourceFile:127)at axr.m(SourceFile:111)at net.minecraft.client.Minecraft.l(SourceFile:1078)at net.minecraft.client.Minecraft.K(SourceFile:574)at net.minecraft.client.Minecraft.run(SourceFile:526)at java.lang.Thread.run(Unknown Source)A detailed walkthrough of the error, its code path and all known details is as follows:----------------------------------------------------------------------------------------- Head --Stacktrace:at java.lang.Thread.start0(Native Method)at java.lang.Thread.start(Unknown Source)at bkf.(SourceFile:110)at axk.a(SourceFile:20)at axr.a(SourceFile:72)at axr.d(SourceFile:127)at axr.m(SourceFile:111)-- Affected screen --Details:Screen name: axkStacktrace:at net.minecraft.client.Minecraft.l(SourceFile:1078)at net.minecraft.client.Minecraft.K(SourceFile:574)at net.minecraft.client.Minecraft.run(SourceFile:526)at java.lang.Thread.run(Unknown Source)-- System Details --Details:Minecraft Version: 1.5.2Operating System: Windows 8 (x86) version 6.2Java Version: 1.7.0_21, Oracle CorporationJava VM Version: Java HotSpot™ Client VM (mixed mode), Oracle CorporationMemory: 994832256 bytes (948 MB) / 1037959168 bytes (989 MB) up to 1037959168 bytes (989 MB)JVM Flags: 3 total; -Xbootclasspath/a:C:\Program Files (x86)\Java\jre7\lib\deploy.jar;C:\Program Files (x86)\Java\jre7\lib\javaws.jar;C:\Program Files (x86)\Java\jre7\lib\plugin.jar -Xmx1g -Xms1024MAABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) usedSuspicious classes: No suspicious classes found.IntCache: cache: 0, tcache: 0, allocated: 3, tallocated: 63LWJGL: 2.4.2OpenGL: Intel® HD Graphics 4000 GL version 4.0.0 - Build 9.17.10.2828, IntelIs Modded: Probably not. Jar signature remains and client brand is untouched.Type: Client (map_client.txt)Texture Pack: DefaultProfiler Position: N/A (disabled)Vec3 Pool Size: ~~ERROR~~ NullPointerException: null

PLEASE HELP!!!

Edit: IT doesn't show me a crash report, so I'm not sure if this is the actual error.

Looks like it just ran out of memory. Try allocating more.

Quote from Builderb0y

Looks like it just ran out of memory. Try allocating more.

idk how to.

And it crashes on startup, so that sucks.

http://lmgtfy.com/?q=how to allocate more memory to minecraft

Quote from Builderb0y

http://lmgtfy.com/?q...ry to minecraft

Just tried that, didn't work.

It says in the error log that it ran out of memory somewhere. If allocating more didn't help, I really don't know what to try next.

You can always go back to the official version though. It might even be fixed by the time the next snapshot comes out.

Quote from Builderb0y

It says in the error log that it ran out of memory somewhere. If allocating more didn't help, I really don't know what to try next.

You can always go back to the official version though. It might even be fixed by the time the next snapshot comes out.

You may want to read the edit in the OP. In the launcher development console-thingy, it says something about the game ending with bad state and google. I don't know about that I don't understand Javanese.

Looks like your edit messed up the spacing. Anyway, the bad state means that it is incapable of running for whatever reason. And google helped with some of the code included with standard java, which is why you see it listed. Another reason minecraft crash logs are hard to read is that after completing the code for it, they rename EVERYTHING with a short random name. akx, aby, bkq, nxz, things like that. It was done that way to prevent people from stealing the code. But in a nutshell, most crash logs follow the same format:

1. The error, usually something like "java.lang.nullPointerException", or whatever the error was. In this case, it was "java.lang.outOfMemoryException"

2. Everything that it's currently doing, where all the lines start with "at"

3. And lastly, everything it knows about your system, such as your processor brand, your graphics card, your RAM, and a bunch of other stuff.

Diagnosing problems can be hard, but like I said before, I would suggest going back to the last version that worked, and waiting for the next version to be released.

Quote from Builderb0y

Looks like it just ran out of memory. Try allocating more.

Whenever I do that, it says that it could not create the Java Virtual Machine.