Minecraft Forums

My Minecraft will not start past the Mojang screen. It goes to an error page and tells me i am Out Of Memory, when I have 8 gigs of RAM. It gives me this error message. Can anyone help please

---- Minecraft Crash Report ----
// I blame Dinnerbone.

Time: 11/16/14 9:11 PM
Description: Initializing game

java.lang.OutOfMemoryError: Java heap space
at cuj.a(SourceFile:402)
at cua.b(SourceFile:238)
at cua.a(SourceFile:77)
at cxh.j(SourceFile:553)
at cxh.a(SourceFile:139)
at cxk.a(SourceFile:23)
at cvt.a(SourceFile:99)
at bsu.aj(SourceFile:437)
at bsu.a(SourceFile:299)
at net.minecraft.client.main.Main.main(SourceFile:120)


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

-- Head --
Stacktrace:
at cuj.a(SourceFile:402)
at cua.b(SourceFile:238)
at cua.a(SourceFile:77)
at cxh.j(SourceFile:553)
at cxh.a(SourceFile:139)
at cxk.a(SourceFile:23)
at cvt.a(SourceFile:99)
at bsu.aj(SourceFile:437)

-- Initialization --
Details:
Stacktrace:
at bsu.a(SourceFile:299)
at net.minecraft.client.main.Main.main(SourceFile:120)

-- System Details --
Details:
Minecraft Version: 1.8
Operating System: Windows 7 (x86) version 6.1
Java Version: 1.7.0_60, Oracle Corporation
Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
Memory: 167526672 bytes (159 MB) / 523501568 bytes (499 MB) up to 523501568 bytes (499 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.8
LWJGL: 2.9.1
OpenGL: GeForce GTX 780/PCIe/SSE2 GL version 4.4.0, NVIDIA Corporation
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: [LB Photo Realism x256 10.0.0-converted-1374012707213.zip]
Current Language: English (US)
Profiler Position: N/A (disabled)

Quote from webrosc »its saying run out of member because your trying to run a x256 Resource Pack without upping the allocated ram.

Use a lower Resource Pack instead, if you musty up the ram allocation you will be limited to around 1.5G due to the fact your running a 32bit OS, you need 64bit to be able to allocts more than 1.5G

Having the ram in your computer is not the same as allocating it, for all minecraft could care you may have 10000G of ram, but its set currently to use 512MB max

Thank you for the reply, I haven't played minecraft for a long time and I am just coming back, how do I remove the resource pack? And also, I am running a 64-bit OS, but I'd rather just remove the resource pack and be able to play.

You can edit the options.txt file in your .minecraft folder and remove the line that configures a resource pack.

Quote from gerbil»

You can edit the options.txt file in your .minecraft folder and remove the line that configures a resource pack.

Alright, got it working. Thanks a lot both of you!

Quote from webrosc»

its saying run out of memory because your trying to run a x256 Resource Pack without upping the allocated ram.

Use a lower Resource Pack instead, if you musty up the ram allocation you will be limited to around 1.5G due to the fact your running a 32bit OS, you need 64bit to be able to allocts more than 1.5G

Having the ram in your computer is not the same as allocating it, for all minecraft could care you may have 10000G of ram, but its set currently to use 512MB max

It is worth noting that this can actually worsen memory issues on a 32 bit system, because the total process memory is limited to 2 GB and Java needs memory for its own needs (from what I've seen with 512 MB allocated Task Manager reports over 1 GB used); in fact, even 1 GB causes out of memory errors if I try using anything higher than Normal render distance, while I have no problem with 512 MB allocated. This is also mentioned in a bug report (gotta love the solution "increase RAM" and the replies saying it doesn't work):

Well my knowledge was based on before Minecraft gained native HD texture support.

Now that it has native support it may to be handled differently now but previously textures got allocated outside the heap (somehow) in the remaining process space on clients modded to handle HD textures. So reducing the heap was the fix usually on systems forced to only be able to run 32-bit java. Now it seems that with 32-bit java if there isn't enough space to fix the textures it will just silently fail and fallback to default.

Regardless I did a few additional tests on 1.6.4. Note that I did it on 32-bit java only. On 64-bit it really isn't needed and the last test I did on 32-bit java actually fails on 64-bit for unknown reasons. Only the 768M test passes for both ends on a 256x texture pack.

Thus, the OP may still be able to use their resource pack, but they need to allocate 768 MB of RAM (in the launcher, click "edit profile", then in the JVM arguments line at the bottom change -Xmx512M to -Xmx768M; I'd also suggest adding -Xms768M so all the RAM available is allocated from the start). (oddly enough, in the tests they did just 256 MB of RAM was enough to run the game (32 bit only); presumably, they were using a medium render distance which loads less chunks, note also that this was for 1.6.4 and 1.8 is much more resource demanding)