New launcher crashes with Java error

[Zacharry Field]

I've been running the new 1.6.4 FTB packs since they came out. All was good at first, but a very recent launcher update now refuses to run the 1.6.4 packs with 1 GB ram allocated to Minecraft.

I know, I know, you shouldn't run modded Minecraft with only 2 GB ram on your system, but it actually runs alright. I can cut out some of the more FPS intensive mods, or really lower down the graphic settings, whatever. The point is that FTB 1.6.4 packs were working fine for me, until this new update prevents me from launching with 1 GB ram allocated. It only runs with 768 MB allocated.

Is this due to the new updates removing their preset parameters for Java? If so, does anyone know what parameter settings would let me use 1 GB again?

Oh, and the exact Java error, given in a popup window, is: "Could not create the Java virtual machine."

 

[TheSandwichMakr]

The update may have done something funky, and it may no have decided to use 32-bit java if it's installed. Post the crash log or console log to pastebin.

 

[Zacharry Field]

I run 32-bit Windows XP, I only have 32-bit Java installed. I have re-installed it as well, just in case.

Here's a pastebin for the FTB Launcher Log: http://pastebin.com/HgpZVEUn
http://pastebin.com/HgpZVEUn
The Minecraft Log had just two lines in it:
"Error occurred during initialization of VM
Could not reserve enough space for object heap"

Not having enough space is extra strange, because I was playing the 1.6.4 packs just earlier today.

 

[Zacharry Field]

I'll note that the previous FTB packs will all run on the 1 GB setting, it's just the 1.6.4 ones that refuse to get past Java starting up.

 

[TheSandwichMakr]

The launcher update is what I think is causing the issue. You can try adding the parameters -Xmx1350M -XXermSize=128M under advanced options. 32-bit java gets around 1.4 gigs of ram so you can give some more to the heap, and take some from the perm space as 256MB is usually not necessary.

 

[lavarthan]

[23:27:12] [INFO] JavaFinder.parseWinJavaVersion:137: Java Version: 1.6.0_29 sorted as: 1.6.0_29 32 Bit Java at : C:\Program Files\Java\jre6\bin\java.exe
[23:27:12] [INFO] JavaFinder.parseWinJavaVersion:137: Java Version: 1.6.0_03 sorted as: 1.6.0_3 32 Bit Java at : C:\Program Files\Java\jre1.6.0_03\bin\java.exe
[23:27:12] [INFO] JavaFinder.parseWinJavaVersion:137: Java Version: 1.6.0_18 sorted as: 1.6.0_18 32 Bit Java at : C:\Program Files\Java\jre1.6.0_18\bin\java.exe
[23:27:12] [INFO] JavaFinder.parseWinJavaVersion:137: Java Version: 1.7.0_45 sorted as: 1.7.0_45 32 Bit Java at : C:\Program Files\Java\jre7\bin\java.exe
[23:27:12] [INFO] JavaFinder.parseWinJavaVersion:137: Java Version: 1.6.0_26 sorted as: 1.6.0_26 32 Bit Java at : C:\Program Files\Java\jdk1.6.0_26\bin\java.exe
[23:27:12] [INFO] JavaFinder.parseWinJavaVersion:137: Java Version: 1.7.0_45 sorted as: 1.7.0_45 32 Bit Java at : C:\WINDOWS\system32\java.exe

Why do you have so many Java versions? You should only have the latest version installed. Remove all the older versions. The newer packs run best on having 2GB+ allocated and thus will have problems running in 32bit. I do not see any error yet, besides having multiple versions of Java installed. Uninstall the other versions of Java and give the pack several minutes or longer if needed. The new packs take a while to install.

 

[Zacharry Field]

A Java error tells me that it doesn't recognize 'permSize=128M' parameter. I tried MaxPermSize, which does work.. but it still fails with the same error as above:

"Error occurred during initialization of VM
Could not reserve enough space for object heap"

Changing to "-Xmx1G -XX:MaxPermSize=128M" gives the same response. I tried -Xmx1G because that's how the parameter is defined with the normal Minecraft 1.6 profile on the default Minecraft Launcher.[DOUBLEPOST=1387603294][/DOUBLEPOST]Okay, I'll try removing the old Java versions. And I can run the new packs alright, and have been doing so since they came out, it's the new Launcher update that changed something.

 

[TheSandwichMakr]

Use -Xmx1350M not -Xmx1G. Using 1G allocates 1 gig, you want to allocate more than a gig (1350M is a bit more than a gig), because it's crashing.

 

[Zacharry Field]

I did use the 1350M setting first, and just tried it again, but it still crashed with the same error message. Now that I removed the other Java versions, it hasn't changed the result at all. It's very strange, I can take the individual mods and add them myself to a 1.6.4 profile in the default Minecraft launcher, and it'll run just fine. It only seems to crash Java when done through the FTB Launcher.

 

[TheSandwichMakr]

The latest version must be bugged then, I'm posting a thread with issues in the launcher feedback section. Sorry I couldn't help :'(

 

[Zacharry Field]

That's alright, thanks for the help anyway! I've been through a ton of FTB issues in the past, I can be patient. At the very least I can make use of the modpack's config settings, since the packs themselves do install just fine.

 

[Dillon845]

That's alright, thanks for the help anyway! I've been through a ton of FTB issues in the past, I can be patient. At the very least I can make use of the modpack's config settings, since the packs themselves do install just fine.

Uninstall all your java's Then reinstall only JRE 64bit (then allocate 1.5gb) or install the 32biut version?

 

[TheSandwichMakr]

Uninstall all your java's Then reinstall only JRE 64bit (then allocate 1.5gb) or install the 32biut version?

He's running 32-bit Windows, so he can't use 64-bit java D':

 

[Dillon845]

He's running 32-bit Windows, so he can't use 64-bit java D':

Oh sorry im really tired its 2 in the morning didnt sleep for 3 days now

 

[TheSandwichMakr]

Oh sorry im really tired its 2 in the morning didnt sleep for 3 days now

Story of my life.