Accepted answer

this may not be an exact solution for your issue, but in my case, i tracked the files that eclipse was polling against with sysinternals procmon, and found that eclipse was constantly polling a fairly large snapshot file for one of my projects. removed that, and everything started up fine (albeit with the workspace in the state it was at the previous launch).

the file removed was:



i had no snap files. going through the help menu installation list, at least 90% of my plugins had the uninstall button deactivated so i could not handle it through there. under startup/shutdown most of plugins were not listed. instead, i had to manually remove items from my plugins folder. wow, the startup time is much faster for me now. so if everything else does not work and you have plugins that are disposable, this could be the ultimate solution to use.


unfortunately, none of these solutions worked for me. i ended up having to create a new workspace, then imported the existing projects into the new workspace. unfortunately, you lose your preferences when doing so (so, remember to export your settings anytime you change them!)


i had a very similar problem with eclipse (juno) on fedora 18. in the middle of debugging an android session, eclipse ended the debug session. i attempted to restart eclipse but it kept haning at the splash screen. i tried the various suggestions above with no success. finally, i checked the adb service (android debug bridge):

# adb devices
list of devices attached 
xxxxxx offline

i know the android device was still connected but it reported it offline. i disconnected the device and shut down the adb service:

# adb kill-server

then i waited a few seconds and re-started the adb service:

# adb start-server

and plugged my android back in. after that, eclipse started up just fine.


no need to delete entire metadata file. just try deleting the .snap file from org.eclipse.core.resources on your workspace folder

ex. e:\workspacefolder\.metadata\.plugins\org.eclipse.core.resources


watch out for zero-byte .plugin files in the {workspace-dir}/.metadata/.plugins folder. i just deleted one in there and it fixed my freezing issues.


what worked for me was this-- on ubuntu

  1. ctrl+f1
  2. ps -e
  3. kill -9 for process ids of eclipse, java and adb


in my case similar symptoms were caused by some rogue git repository with a ton of junk system files.

universal remedy, as mentioned above, is to use process monitor to discover offending files. it's useful to set the following 2-line filter:

  • process name is eclipse.exe
  • process name is javaw.exe


i had a similar problem after i updated eclipse on mavericks. eventually i found that in the eclipse plugins directory the jar had version numbers at the end. i removed the version number from the name and it all started fine :)


also look at

99% recommended solution works.... (i.e. removing .snap file) but if it did not worked then we have to try to remove indexes folder and further workbench folder.


this may help

in your eclipse,

1) go to help

2) click eclipse marketplace

3) search - optimizer

install "optimizer for eclipse"

enter image description here


in ubuntu eclipse -clean -refresh worked for me for eclipse 3.8.1


it can also be caused by this bug, if you're having eclipse 4.5/4.6, an eclipse xtext plugin version older than v2.9.0, and a particular workspace configuration.

the workaround would be to create a new workspace and import the existing projects.


well, i had similar behaviour while starting eclipse over x11. i forgot to tick the enable x11 forwarding in my putty.


in my case deleting the .metadata folder of the workspace worked. i am using eclipse luna service release 2.


my solution is to remove this dir:


what is did was first remove (move it to a save place) all from .metadata. eclipse started all new (all my settings gone). then i added bit by bit back into the .metadata dir until it dit not work again. this way i found i only had to remove this dir. and now eclipse started with all my settings still in place.

it seems that in the file in this dir the windows which should be opened on startup are listed and some how it could not find one off them so it hung. why i'm unclear because the file which in complained about in the logging was on my filesystem.


my freeze on startup issue seemed to be related to the proxy settings. i saw the username\password dialog on startup, but eclipse froze whenever i tried to click ok, cancel, or even just click away from the dialog. for a time, i was seeing this authentication pop-up with no freeze issue.

to fix it, i started eclipse using a different workspace, which thankfully didn't freeze on me. then i went to window --> preferences --> general --> network connections. i edited my http proxy entry and unchecked "requires authentication". then i started my original problematic workspace, which launched this time without freezing. success!

i had no further issues when i re-opened my workspace, and was able to re-enable authentication without having a problem. i didn't see the username\password pop-up anymore on start-up, so there's a chance my authentication info was fubar at the time.

using: myeclipse, version: 2016 ci 7, build id: 14.0.0-20160923


i did a lot of these solutions and none seemed to work for me. what finally did work was to restart my mac. duh. i noticed that my jconsole also seemed to be stuck which made me immediately go for a restart because it seemed to be java related as opposed to eclipse specifically.


java version could be problem:

i tried few answers given above. but it didnot work. but meanwhile i was trying them it clicked to me that i switched the java version for some other stuff & forgot to switch back.

once i jumped back to the previous version. eclipse started working for me.


the freezing / deadlock can also be caused by this bug on gtk3 + xorg

can be workarounded by using wayland session, although in my case eclipse fails to detect reasonable font for some reason and looks like this:




windows -> preferences -> general -> startup and shutdown

is refresh workspace on startup checked?


i just had problems with eclipse starting up. it was fixed by deleting this file:

rm org.eclipse.core.resources.prefs

i found in .settings


uft causing issues with rdz (eclipse based) after install these suggestions will allow to work around this situation even with the environment variables in place and with corresponding values.

note: conflicting application will not be recognized in a java context because it is being excluded from the java support mechanism.

  1. impact: excludes add-ins support from hooking to conflicting application executable via windows registry editor requirement: the application must be started by an exe file, except java.exe/javaw.exe/jpnlauncher.exe


a. locate the executable filename of the application conflicting with add-in(s) support. either use the task manager or the microsoft process explorer.

b. open windows registry editor.

c. navigate to: hkey_local_machine\software\mercury interactive\javaagent\modules for 32bits applications on windows x64: hkey_local_machine\software\wow6432node\mercury interactive\javaagent\modules

d. create a dword value with the name of the conflicting software executable filenmae and set the value to 0.

updated registry


removing *.snap (mine is *.markers), --clean-data or move workspace folder seems all did not work for me.

as my eclipse stopped working after i installed and switched my keyborad input to hime, i went back to fctix and it worked.


check that the workspace launcher hasn't opened on your tv or some other second monitor. it happened to me. the symptoms look the same as the problem described.


i did this:

  1. cd to .metadata.plugins\org.eclipse.core.resources
  2. remove the file .snap
  3. noticed the progress tab was doing something every few seemed stuck
  4. exit eclipse (do not file|restart here or you have to go back to step 1 again)
  5. open eclipse again.

using -refresh or -clean when starting eclipse did not help.


on mac os x, you start eclipse by double clicking the eclipse application. if you need to pass arguments to eclipse, you'll have to edit the eclipse.ini file inside the eclipse application bundle: select the eclipse application bundle icon while holding down the control key. this will present you with a popup menu. select "show package contents" in the popup menu. locate eclipse.ini file in the contents/macos sub-folder and open it with your favorite text editor to edit the command line options.

add: "-clean" and "-refresh" to the beginning of the file, for example:



since i don't have a .snao or .prefs file in .metadata.plugins\org.eclipse.core.resources folder (running on os x), what did the trick for me was copy the .project folder to old.project, start eclipse, and check

windows -> preferences -> general -> startup and shutdown -> refresh workspace on startup

as proposed by matt b. after that, i closed eclipse, renamed the folder old.projects back to .projects and after that everything worked fine again.


i tried all of the answers in this thread, and none of them worked for me -- not the snap files, not moving the projects, none of them.

what did work, oddly, was moving all projects and the .metadata folder somewhere else, starting eclipse, closing it, and then moving them all back.


i also had luck with removing the *.snap files. mine were located in a different directory than mentioned in the posts (below).

<eclipse workspace>/.metadata/.plugins/org.eclipse.core.resources/.projects

consequently, the following unix cmd did the trick:

find <eclipse_workspace>/.metadata/.plugins/org.eclipse.core.resources/.projects  -name "*.snap" -exec rm -f {} \;


i had a similar problem with a rather large workspace in 3.5 and no .snap-files anywhere to be seen. "windows -> preferences -> general -> startup and shutdown -> refresh workspace on startup" seems to be a workspace-related setting and so i couldn't change it for the workspace that was causing the hang.

running eclipse with the command line parameter -refresh and then changing the setting seems to do the trick.


i used eclipse -clean -clearpersistedstate and that worked for me.

warning: this may remove all projects from the workspace.


this one works for me:

another, and a bit better workaround which apparently works:

  1. close eclipse.
  2. temporary move offending project somewhere out of the workspace.
  3. start eclipse, wait for workspace to load (it should).
  4. close eclipse again.
  5. move the project back to workspace.

source: eclipse hangs while opening workspace after upgrading to gwt 2.0/google app engine 1.2.8


you can try to start eclipse first with the -clean option.

on windows you can add the -clean option to your shortcut for eclipse. on linux you can simply add it when starting eclipse from the command line.


in my case (juno) i had to do this:

find $workspace_dir/.metadata/.plugins/org.eclipse.core.resources/.projects \
-name .indexes -exec rm -fr {} \;

that did the trick.

initially i thought it was a problem with mylyn (i experienced these freezes after i started using its generic web connector), but the problem appeared even after uninstalling the connector, and even deleting the .mylyn directories.

edit: i also managed to restart eclipse by deleting just one file:

rm $workspace_dir/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi

that worked fine, without any indexes involved. only the workbech, which i personally don't mind that much.



  1. cd to <workspace>\.metadata\.plugins\org.eclipse.core.resources
  2. remove the file *.snap (or .markers in indigo)

Related Query

More Query from same tag