Minecraft Forums

I have a forge installed with over 132 mods, so I needed to increase the initial heap size to 1Gb. It worked before, but when I tried to launch Minecraft today it came at me with a "Could not reserve enough space for object heap" error. I'm pretty sure even 32 bit Java could manage 1 Gb, but just i case, I made sure I was running on 64 bit Java, and even moved the 32 bit Java to a temporary path to make sure that is the case. It seems to give me that error for any heap size larger than 512 Mb. I would try running it through command line, but the script got a bit more complicated since 1.5 or 1.6.

Technical stuff:
Windows 8 64 bit
JRE 7 64 bit
JVM arguments: -d64 -XX:PermSize=512m -XX:MaxPermSize=512m -Xms1G -Xmx2G
Minecraft 1.6.4
Forge 9.11.965

I would post logs if it generated any.

Well there are no Forge logs since the JVM crashes on the instant it gets called to open. I tried finding any Java crash logs resulting from the crash, but found none. The screenshot is the best log I can provide.

Updated to JRE 8 just in case

I have 8 Gb of RAM

Out of Memory. Got logs this time.

Forge crash log: http://pastebin.com/Lui0bh25
Minecraft crash log: http://pastebin.com/Mkn8Ch37

Yea I'm using a custom launcher. It got updated recently and this has been happening ever since. How can a launcher affect the execution of a JVM while passing arguments that clearly shouldn't be causing the problem (unless it's false data and it's setting another value for heap)? I want to test the theory of whether the launcher I'm using is modifying the arguments in the background by running vanila from cmd. While I know the code for the earlier version of minecraft (such as 1.4.7), Mojang switched up the file structure since and is a little more complicated. Have any clue how?

Tried this but it just silently terminates with no error.

"C:\Program Files\Java\jre7\bin\javaw.exe" -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -XX:MaxPermSize=256m -Xms512m -Xmx3G -Djava.library.path="C:\Users\abraker\AppData\Roaming\.minecraft\versions\1.6.4-Forge9.11.1.965\1.6.4-Forge9.11.1.965-natives-388212049436059" net.minecraft.launchwrapper.Launch --username abraker95 --session XXXXXXX --version 1.6.4-Forge9.11.1.965 --gameDir "C:\Users\abraker\AppData\Roaming\.minecraft" --assetsDir "C:\Users\abraker\AppData\Roaming\.minecraft\assets\virtual\legacy" --tweakClass cpw.mods.fml.common.launcher.FMLTweaker

I migrated to using the Magic Launcher. Works like a charm. I don't know how the other launcher is putting in the memory wrong (even the logs don't show anything abnormal), but I'm glad I got this sorted. Thank for the help grimallq!

Unless I figure out how to edit the title, this thread can be marked solved.