Eclipse workspace crashes on startup

不羁的心 提交于 2019-11-28 11:57:56
DineshM

I faced the same problem. I followed these steps and it's working fine,

  1. Go to your workspace e.g. C:\Workspace

  2. Then open .metadata.plugins folder from your workspace.

  3. Delete below 2 folders,

    • org.eclipse.e4.workbench
    • org.eclipse.equinox.p2.ui.sdk

Eclipse should start after this.

Gaytan

Solves the problem by eliminating the workspace\.metadata\.plugins\org.eclipse.e4.workbench directory.

What I did when I had this problem was deleting the .lock inside the crashing workspace's .metadata folder.

Worked as a charm.

I had the same problem after opening a Kepler workspace with Luna and then switch back to Kepler. Seems that Luna added some data unexpected by Kepler.

I had to remove the .metadata folder and configure the workspace again.

Error Got removed by deleting org.eclipse.e4.workbench in workspace.metadata.plugins folder... :)

Friends,

For me the only solution was a simple adjustment in the eclipse.ini.

The file located in the root folder of the Eclipse installation.


Before the -vmargs line add the following:

-vm

C:\Program Files\Java\jre7\bin\javaw.exe

Staying like this:

...

-vm

C:\Java\JDK\1.8\bin\javaw.exe

-vmargs

...


Specifying the JVM

One of the most recommended options to use is to specify a specific JVM for Eclipse to run on. Doing this ensures that you are absolutely certain which JVM Eclipse will run in and insulates you from system changes that can alter the "default" JVM for your system. Many a user has been tripped up because they thought they knew what JVM would be used by default, but they thought wrong. eclipse.ini lets you be CERTAIN.

The following examples of eclipse.ini demonstrate correct usage of the -vm option.

Note the format of the -vm option - it is important to be exact:

  • The -vm option and its value (the path) must be on separate lines.
  • The value must be the full absolute or relative path to the Java executable, not just to the Java home directory.
  • The -vm option must occur after the other Eclipse-specific options (such as -product, --launcher.*, etc), but before the -vmargs option, since everything after -vmargs is passed directly to the JVM.
  • For the 32-bit Eclipse executable (eclipse.exe on Windows) a 32-bit JVM must be used and for the 64-bit Eclipse executable a 64-bit JVM must be used. 32-bit Eclipse will not work with a 64-bit JVM.

More about eclipse.ini configuration: https://wiki.eclipse.org/Eclipse.ini


I hope this helps...

Good Luck!

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!