Minecraft Forums

ok, I'm having a really dumb issue with this new launcher.

it runs 1.5.2 just fine if I use magiclauncher and set the memory to 512mb-1G normally, but it doesn't use the launcher to load the game.

BUT when I try to use the regular Minecraft.exe (Yes, the new updated one...) it tells me the java virtual machine can't start...which I know is stupid.

I have tried using the various commands in the prompt to start it like this : java -Xmx1024M -Xms1024M -jar "Minecraft.exe"

& this: java -Xmx512M -Xms512M -jar "Minecraft.exe"

but it still says there's not enough memory. and it's ing me off.

I built this computer myself. it has 2 gigabytes of memory, a 3.0ghz celeron intel CPU with a radeon 7750 video card & more than enough HD space to run and has ran minecraft successfully in the past. it runs on a 32 bit java system and the OS is win7 (32bit)

it will run 1.5.2 using the minecraft Magiclauncher for some reason, but not with the normal .exe of minecraft which will not allow me access to the new launcher that Mojang suggests.

so...if there's any suggestions on how to fix this java virtual machine problem...I'd love to hear em.

and before any ask me what version of java I'm using...it's the newest update we got a couple days back.

Use the new launcher, edit the profile you are using. Check the JVM arguments checkbox and paste in "-Xmx512M -Xms512M" to the text box.

it doesn't load the normal launcher at all. and I've used those command line modifiers.

It won't let me even see the new launcher much less load. you have read my first post right?

---> "BUT when I try to use the regular Minecraft.exe (Yes, the new updated one...) it tells me the java virtual machine can't start...which I know is stupid.

I have tried using the various commands in the prompt to start it like this : java -Xmx1024M -Xms1024M -jar "Minecraft.exe"

& this: java -Xmx512M -Xms512M -jar "Minecraft.exe" <---


the problem is the normal client WILL NOT LOAD! ...stupid java...

It's that the virtual machine will not start even when I allocate LESS memory to it.

I'm having the same issue. I used to be able to open the old one with the following code as a .BAT, but...obviously, the launcher version has changed, so I don't know what to put there now!

cd C:\Documents and Settings\myprofilenamehasbeenremoved\Desktop
java -Xmx512M -Xms256M -cp Minecraft.jar net.minecraft.LauncherFrame

Quote from Tedster

If his problem is exactly the same as mine (and it sounds like it is), we cannot load the new launcher.

At all. The 'cannot create java virtual machine' pops up before the launcher can even load.

I've closed every program I could. If you have READ CAREFULLY, our issue here is the launcher WILL NOT LOAD due to the java executable saying it's not got enough memory. any suggestions that we change the variable within the launcher is utter lunacy...JAVA will not run the code far enough to even get to that point. it just gives us the 'could not start' message.

It's not a memory issue at all, there's more than enough memory.

My machine will run 1.5.2 no darn problem! it's the new update that it refuses to run.

won't run through command line, I've checked java's options, everything I can figure I've tried. I'm hoping the community has some possible solution. not the first time I've had issue with the java machine not loading either, but the magiclauncher workaround ain't cutting it.

Still nothing. And I've tried having it read the .JAR, the .EXE, with and without the bit of code for 'net.minecraft.LauncherFrame'.

that's what I had to do, it crashed out the first two times, but after making the batchfile and changing it to 512m it seems to be co-operating with me now. not liking that I need the cmd window up while it runs, but small sacrifices eh?


once the batchfile ran I was able to set the memory allocation in the new launcher itself. still working with it to reverse engineer the problem and submit a bug report on the results.

but so far...it needs a bit of rough loving to get working good.

I don't know WHAT I did, but the launcher finally opened for me. Set the memory limits, and it seems to now work! Issue seems solved for me. <3