Eclipse startup hang, “Android SDK: resolving erro

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: resolving error markers" furthermore, if I try to interact with it, it freezes completely and I am forced to force quit.

This is the progress dialog:

I find it odd that it needs to resolve the error markers multiple times but I assume this is just for each project in my workspace.

this is my eclipse.ini:

Other things to note being that all that currently exists within my workspace is an Android Application, an App-engine endpoint project for the before application, and 4 needed referenced libraries. All mentioned projects are open. Is this a matter of me overloading the IDE or perhaps there is some loop I threw it into? I find it hard to imagine that this is a unique circumstance.

UPDATE: When I delete the app engine endpoint project from the workspace and restart eclipse, it loads fine. When I bring it back in, all good. But when I restart from there, it goes into error loop again. I am convinced that I have a circular reference in there somewhere but I cant figure out where. Thanks for your help.

Answer 1

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 2

figured it out a couple days ago and forgot to inform y'all.

all I needed to do was save the projects to some other directory if you have not already. Delete it from your workspace and also delete the app engine endpoints project.

Re-import the android project and copy into workspace. set the java build path and everything else (if it says 'project master' control click -> team -> disable) everything should look fine. Then, delete all references to the app engine project, this means folders called 'endpoint-libs/libcontainers...'

This will break your project everywhere you reference the data model

Now, re-import the app engine project and make any necessary changes so that it doesn't have build errors (warnings may be OK).

Control click -> generate cloud endpoint client library. The libraries in the original project will be replaced.

Not entirely sure what caused this but for the time being it has been working beautifully.

Answer 3

I frequently facing this problem. And my final approach was..

1. First open TaskManager by pressing CTRL+ALT+DEL and delete all instance of adb.exe. if problem doesn't solve then go to next step without closing taskManager.

2. Close Eclipse and also check it shouldn't be running in TaskManager(also finish its process).Then Open %USERPROFILE%/ on Windows or simply ~ on Linux/OS X (You can locate this folder from the Desktop). then open .android folder and delete cache folder and ddms.cfg and start Eclipse. If still your problem doesn't solve follow.

3. If your problem doesn't solve by following above method then go to workspace folder and delete as suggested by this Answer

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

4. If problem still doesn't solve then Pray to God.

Answer 4

I solved the issue with this (from your eclipse folder):

eclipse -clean -refresh

I followed this url: http://tekhoow.blogspot.com.es/2013/06/eclipse-stuck-at-android-sdk-resolving.html (but the eclipse command was enough for me)

There is also another stack question with the same topic and say the same: "Clean all projects in your workspace and restart Eclipse to solve this problem." How to Resolving error markers Eclipse Android SDK

Answer 5

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 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