Just downloaded the latest version of Eclipse version 3.6.1 from Eclipse.org. After zip file extraction, I was ready to check out the latest Eclipse; unexpectedly, I ran into an error prompt read as “Failed to create Java Virtual Machine”. Bam, why?!?!
After some tinkering, I was lead to the eclipse.ini file and found out some add-on configuration added in this latest version. "–launcher.XXMaxPermSize”. By removing the dafault value 256m, I’m now able to run it. 
My eclipse.ini file now read as below:
plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
–launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.1.R36x_v20100810
-showsplash
org.eclipse.platform
–launcher.XXMaxPermSize
–launcher.defaultAction
openFile
-vmargs
-Xms40m
-Xmx384m
For more information about the latest eclipse.ini, check out the link below:
http://wiki.eclipse.org/Eclipse.ini
http://wiki.eclipse.org/FAQ_How_do_I_increase_the_permgen_size_available_to_Eclipse%3F
I don’t get paid for writing blog posts. Your “Votes” and “Like” is my only motivation, so please “Like” it if you found this information useful. Cheers!!!
Check out what other says about this post by clicking at the title of this post.
Like this:
Filed under: Software Development, Eclipse, Failed to create Java Virtual Machine
Thanks!
cheers mate
Fixed my problem, thanks!
This initially fixed my issue, but then Eclipse crashed soon after and now I get the issue again. And this time I can’t get past it!
I have no idea how this happened all of a sudden.
Jerry, which version of Eclipse you downloaded? Did you tried to re-install your Java virtual machine?
Thank you very much.
It’s work!!
I had the same problem after increasing my heap size in the ini file. After I removed the default value for the perm size it worked fine.
Thanks you.
Thanks, your advice helped me.
I am just wondering how the –launcher.XXMaxPermSize 256m got into the eclipse.ini file, because I never changed the file myself.
Hellu Luis,
Glad that it helps. The -launcher string was added by default when we download the installer from Eclipse.
I noticed in combination with VE 1.5 and some open VE edit windows that this was blocking the startup of exclipse. I Applied the suggestion by removing the value 256m. But that triggers a running eclipse at 100% CPU. jvisualvm.exe showed 100% time in GC. So I changed to a value of 128m and now all started fine. jvisualvm showed that for Eclipse 3.6.1 EE and some extra plugins, I need at least 80m in Perm. The default might be too low (removing the 256m values).
Also be careful with the -XmsNNNm option. It will be applied to each javaw.exe for each opened VE editor. So you might run out your OS memory quickly.
@Eremmel, that explain one of the question sent to me days (via email) earlier on this topic. THANKS for sharing!! Hope your input will help others as well.
I just wanted to thank you for creating this post – I did what you suggested and eclipse is now working fine. I’m very gratfeul!
Helen
Thanks for creating this post. I did what you suggest and eclipse is now working fine. Thanks so much!
Helen
@Helen, no problem.
Thx, it’s really works!!!!!!
It really worked. Thanks a lot.
thanks!
Thanks!!!
GOOD & CLEAN Solution!
Thx!
GOOD & CLEAN Solution!
Thx!
Thank you!
[...] The busiest day of the year was November 19th with 215 views. The most popular post that day was Eclipse: Failed to create Java Virtual Machine. [...]
Thank you very much, it helps me so much!
Thank you for this aid. It has shortened my startup time with Eclipse immensely.
thanks
Thanku so much u saved me….:)
Thanks it worked. Cheers!!!
Thanks
Ditto, this worked for me also.
Thanks..
Thanks…
Thanks It worked
Thanks a lot.
I am able to run Eclipse by removing 256M.
Thanks again.
Thanks a lot , i am able to run Eclipse now
Thanks a lot.
It worked!
Its working now thanks a lot
Thanks, it really saved my day!
Thanks,
but in my eclipse.ini file I also remove the last parameter :
-Xmx384m,because without that it still didn’t work!
But however thank you very much
Thanks , it worked
yeah just remove the default value 256 from –launcher.XXMaxPermSize 256m
and the newly added heap size wud automatically become the default one…
it wud wrk fine then……..Gud LUCK
Thanks. That resolved my same issue.
I found that the Eclipse puts 256m on a separate line.
I changed it to “–launcher.XXMaxPermSize 256m”
It works too.
Sorry, guys
My bad. Please ignore my change. With the change, the Eclipse will report error at the exit time.
@Jun, thanks for sharing though
You can also supply the VM Arguments by navigating to Window->Preferences->Java->Installed JREs and then select the (current) JRE click Edit button. Provide the VM arguments such as “-Xms256m -Xmx512m -XX:PermSize=512m” (these values changed based on your requirement) in the “Default VM Arguments” text field.
Thanks
Dandapani Parasa
Thank you! I just allowed one of Aptana’s updates to run. A restart of Aptana gave me that message. Making the change you suggest fixed it. Thank you, thank you!
This actually works…Thanks a lot for great comment…This post has helped me a lot
I just had the same error, and the problem was that the line read 256M instead of 256m. That solved the problem for me.
Right on the spot, thanks
Thanks a lot, dude.
This worked for me too …
Add the -vm argument in the eclipse.ini file. Eclipse will then locate the JVM and it will work fine.
-startup
plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
–launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.1.R36x_v20100810
-product
org.eclipse.epp.package.jee.product
–launcher.defaultAction
openFile
–launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
–launcher.XXMaxPermSize
256m
–launcher.defaultAction
openFile
-vm
C:\Program Files\Java\\bin\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m
Thanks, great help there!
In my case, @Narendran’s way works. Thanks.
dude.. you made my day man… after a long time.. i got this eclipse issue fixed.. thanks a lot man…:)
Thanks!
thanks
problem solved.
Thanks, Solved My Problem
thanks buddy ..problem solved
thanks man, problem solved
Thanks! I’m now verry happy!
Works like a charm!!! Thanks…
thanks buddy!!!!!! it worked:-)
Thanks a lot for your information….such a nice examination
it worked thanks a lot. by the way how come this value gets added to the ini file?
Wow thanks a lot, quick fix indeed!
nice!
Süper. Thanks for this article .
It works!!!!!!!!!!!!
Nice Job Dude!
It worked for me too!!
The problem started after I installed another eclipse and for that changed the Java_Home path to 1.6 where as the original eclipse used to point to 1.5
After the machine restarted, the original eclipse used to give the error message(JVM something). I removed the xxpermsize and it started working again.
Thanks! It worked like a charm.
Thanks a million ! Helped start the myEclipse 10.
Have 1 question
I increased Xms and Xmx values. Do they really apply to all java processes spawned ?
Correction, removing that value did not start the myEclipse. I had to restore the original set of values
-Xmx768m
-XX:MaxPermSize=256m
Thank Q So Much….:)
Thank you Boss, Really helped me a lot.
After a lot of struggle, your tips really worked for me
Thanks! Totally worked! But, why? My version was the windows 32 bit indigo jee
thanks its save my lots of time.