Minecraft Forums

It gets to the mojang screen and after a few seconds it crashes, crash log is below

---- Minecraft Crash Report ----
// I feel sad now

Time: 4/23/15 4:10 PM
Description: Registering texture

java.lang.OutOfMemoryError: Java heap space
at cuj.a(SourceFile:281)
at cuj.a(SourceFile:271)
at cuj.a(SourceFile:205)
at ctv.a(SourceFile:47)
at cug.a(SourceFile:56)
at cug.a(SourceFile:38)
at btw.<init>(SourceFile:59)
at bss.ak(SourceFile:390)
at bss.a(SourceFile:302)
at net.minecraft.client.main.Main.main(SourceFile:124)

A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Stacktrace:
at cuj.a(SourceFile:281)
at cuj.a(SourceFile:271)
at cuj.a(SourceFile:205)
at ctv.a(SourceFile:47)

-- Resource location being registered --
Details:
Resource location: minecraft:textures/font/ascii.png
Texture object class: ctv
Stacktrace:
at cug.a(SourceFile:56)
at cug.a(SourceFile:38)
at btw.<init>(SourceFile:59)
at bss.ak(SourceFile:390)

-- Initialization --
Details:
Stacktrace:
at bss.a(SourceFile:302)
at net.minecraft.client.main.Main.main(SourceFile:124)

-- System Details --
Details:
Minecraft Version: 1.8.1
Operating System: Windows 8.1 (x86) version 6.3
Java Version: 1.8.0_45, Oracle Corporation
Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
Memory: 13801376 bytes (13 MB) / 60424192 bytes (57 MB) up to 60424192 bytes (57 MB)
JVM Flags: 7 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx3G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M -Xmx64M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.8.1
LWJGL: 2.9.1
OpenGL: Intel(R) HD Graphics 4000 GL version 4.0.0 - Build 10.18.10.3308, Intel
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.

Using VBOs: No
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: []
Current Language: English (US)
Profiler Position: N/A (disabled)

Okay so you may have a lot of memory, but is it all directly aimed at MC? Heres what you got to do to fix it
1.Open Up The Launcher

2.Click On Edit Profile

3.Check the JVM Arguments box at the bottom

4. Erase everything inside and write -Xmx6G

~I wrote 6 just as an indicator, you should write half of your GB in it. For Ex. If I have 16 I would write -Xmx8G
Hope this helped!

Here's your problem right here:

"Operating System: Windows 8.1 (x86) version 6.3"

You've got a 32 bit operating system, which means, while you can dedicate a whole 4 gb of ram to MC, you really can't, as Windows 8.1 uses ~1.5 gb, other background stuff will take another ~.5-1 gb, which leaves about 2 gb for mc. I'd suggest lowering the ram amount to 2 or 1 gb or somewhere inbetween. 32 bit systems are really being phased out, and don't run effectively anymore.

You've got multiple problems now.

1) As noted by jptetch you have a 32bit OS, therefore your attempt to use 3G will never work, but will cause a failure to create the JVM.... if that option were actually being used, which it isn't. You will find that you can't use more than around 1.5G successfully.

2) Your actual problem is that your max heap is configured to be 64 Megabytes. So dramatically inadequate I'm shocked that MC got to loading tectures.

JVM Flags: 7 total;
-XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump
-Xmx3G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode
-XX:-UseAdaptiveSizePolicy -Xmn128M -Xmx64M

I have no clue as to why the crash log is saying i have a 32 bit system. It is actually my friend's computer and the first thing i checked was that it was a 64 bit system (which it was). And about what gerbil was saying, i had attempted to change the max heap but no matter how much i increased it by, it still did not work.

Do you have 32 or 64 bit java?

You need 64 bit.

Hmmm... Im not sure if that entirely true but that also may indeed be the case.

No matter how large an Xmx value you put on the line, when there are TWO of them on the line, like there is, the lowest one will control.

In the crash dump you provided you were trying to use a 3G heap, but that did not matter since there was a second Xmx parameter setting the heap to the much lower value of 64Megabytes.

I do have 64 bit java..

I see what you are saying gerbil, i will try to change that and report back.

The 32-bit OS is not true. its means that your java installation is running on 32-bit, you can get the 64-bit installation HERE