Eclipse startup hang, “Android SDK: resolving error markers”

Question

I am aware that other people have tried to resolve this issue but have thus far found a suitable answer.

The error is, on start up, eclipse gets hung up on \"Android SDK

Answer 1

go to the eclipse folder with cmd,(Shift+right click on eclipse folder and chose open with command promt) then type "eclipse -clean -refresh "

Answer 2

There is a very simple way of invoking the above answers on Mac OSX:

cd workspace

rm ./.metadata/.plugins/org.eclipse.core.resources/.projects/*/.markers

(or)

rm ./.metadata/.plugins/org.eclipse.core.resources/.projects/Project-Name/.markers

cd eclipse.app/Contents/MacOS

./eclipse -clean -remove

Answer 3

I used the answer above - first installing cygwin to get the Unix style "find" installed (note that the DOSbox "cmd" version of "find" does not work - in the following line at the top of your Eclipse workspace that hangs:

find . -name .markers -print -exec rm -i {}

Note that the "-i" specifies "interactive" remove - and will confirm each ".markers" file that is to be removed. Then I followed this with a

./eclipse.exe -clean -refresh

in the eclipse folder. I will check again (after the next hang :-) to see if just the second line is all that is necessary. Anyway eclipse is happy again and so am I! Note that installing the full cygwin package takes a while (many hours) - but it is worth it - just start the install at the end of the day and let it run overnight...

Answer 4

This problem made me crazy until I found below, if I didn't post the answer, I am not a man! Hope this helps if you are also going crazy

I found from Eclipse Stuck at "Android SDK: Resolving error markers":

cd [my workspace folder]

cd .metadata

find . -name .markers -exec rm {} \;

eclipse -clean -refresh

if you are in win32

FOR /F "tokens=*" %%G IN ('DIR /B /AD /S .markers') DO RMDIR /S /Q "%%G"

Answer 5

This has happened to me before.There are errors in the libraries related to the Google App Engine project, what you need to do is close Eclipse, go to your workspace and move every other project not related to the Google App Engine project to another location on your computer, then start Eclipse and make sure you resolve all the issues with the backend project ,then copy the other projects back to your workspace.

Answer 6

After trying all suggested ways, the only way solved my problem was deleting this file:

/workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi

Original answer