Launching Eclipse Hangs, “Android SDK: Eliminating Error Markers”

Question

I know that other people tried to solve this problem, but still found a suitable answer.

Error starting eclipse gets stuck on the “Android SDK: removing error markers”, in addition, if I try to interact with it, it completely freezes, and I am forced to shut down.

This is a progress dialog:

It seemed strange to me that he needed to resolve error markers several times, but I assume that this is simple for every project in my workspace.

this is my eclipse.ini:

Other things to consider are that all that currently exists in my workspace is an Android app, an app endpoint project for the app before and 4 necessary link libraries. All specified projects are open. Is this a matter of overloading the IDE, or is there perhaps some kind of loop in which I entered it? It’s hard for me to imagine that this is a unique circumstance.

UPDATE: When I delete the application engine endpoint project from the workspace and restart eclipse, it loads fine. When I return it, everything is fine. But when I restart from there, it falls into the error cycle again. I am convinced that I have a circular link somewhere, but I cannot figure out where. Thanks for your help.

Answer 1

This problem went crazy until I found below, if I had not posted the answer, I am not a man! Hope this helps if you're crazy too

I found from Eclipse Stuck in the "Android SDK: Resolving Error Tokens" :

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 2

I solved the problem 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 for the eclipse command I had enough)

There is another question on the stack with the same topic and say the same thing: " Clear all projects in the workspace and restart Eclipse to solve this problem ." How to resolve Eclipse Android SDK error markers

Answer 3

After trying all the suggested methods, the only way to solve my problem is to delete this file:

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

Original answer

Answer 4

I had the same problem and found a solution by running "eclipse.exe -clean -refresh" from the cmd prompt. The above solution includes other commands executed in the .metadata folder, which does not apply to all versions of Eclipse. I am using the Eclipse IDE for Android Developers 23.0.2.1259578.

Answer 5

There is a very simple way to invoke 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 6

This has happened to me before. There are errors in the libraries associated with the Google App Engine project, you need to do 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 7

I realized this a couple of days ago and forgot to tell y'all.

all I needed was to save the projects to another directory, if you hadn’t done so already. Delete it from the workspace, and also delete the endpoint project of the application engine.

Re-import the android project and copy it to the workspace. set the java build path and everything else (if it says that the "project wizard" controls click -> command -> disable), everything should look fine. Then remove all links to the application engine project, this means that the folders are called "endpoint-libs / libcontainers ..."

This will ruin your project wherever you refer to the data model.

Now re-import the application engine project and make the necessary changes so that it does not have build errors (warnings may be in order).

Control click → create client endpoint library. Source project libraries will be replaced.

Not quite sure what caused this, but so far it works great.

Answer 8

Great theme !!

After reading all the answers. I found a simple solution and it works fine on Windows 7.

I created the file "eclipse_start.bat" with these simple commands:

 cd /d C:\eclipse (the directory where is the eclipse.exe file) eclipse -clean -refresh cmd 

Every time I have to start Eclipse, I run this file, so the program starts without problems.

I tried another solution. I added this line to the "eclipse.ini" file before any other line

 -clean -refresh 

That way I can run Eclispe directly with the same result, but in a cleaner way.

Thanks everyone!

Answer 9

I have a simple solution without code. Stop the "Resolve error markers" process with the red button, then uncheck the "Automatically create" (Project → Build Automatically), close Eclipse and open it again. Check again Automatically create.

Sometimes this happens again, then I do the same process. Boring, but it works.

Answer 10

Try moving to the workspace folder, in \ workspace.metadata.plugins \ org.eclipse.core.resources.projects You will see folders with your projects. Open each folder and delete the ".markers" files. After restarting Eclipse

Answer 11

Nothing helped me, but then I went to .metadata / .plugins / org.eclipse.core.runtime and deleted files:

 com.android.ide.eclipse.adt.prefs com.android.ide.eclipse.ddms.prefs 

Eclipse started normal again.

Answer 12

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

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

Note that “-i” indicates an “interactive” remove - and will confirm each .markers file that needs to be removed. Then I followed him with

./eclipse.exe -clean -refresh

in the eclipse folder. I will check again (after the following freeze :-) to see if only the second line is needed. In any case, the eclipse rejoices again, and so do I! Please note that installing the full cygwin package takes some time (many hours) - but it's worth it - just run the installation at the end of the day and let it work for the night ...

Answer 13

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

Answer 14

You must remove the .marker file from your project, which exists in .metadata.plugins \ org.eclipse.core.resources.projects (your entire project).

Answer 15

So, on a Mac, with Eclipse ADT, the cleanup and update method helped. Here are some small changes:

Go to ADT Location (if Android) -> Eclipse.app -> MacOS In this directory you should find eclipse. Enter the following command and you should be fine:. / eclipse -clean -refresh

Answer 16

Create a text document in the Eclipse installation folder. Paste this command and update it with the name of your folder

"C: \ The folder where Eclipse \ eclipse \ eclipse.exe is installed" -clean -refresh

Rename it to CleanEclipse.bat and run it every time you have this problem. Save you a lot of time!

Answer 17

I often run into this problem. And my last approach was ...

• First open TaskManager by pressing CTRL + ALT + DEL and delete all instances of adb.exe . if the problem TaskManager , continue to the next step without closing the TaskManager .

• Close Eclipse, and make sure that it should not start in the TaskManager (it will also terminate the process). Then Open% USERPROFILE% / on Windows or just ~ on Linux / OS X (you can find this folder from Desktop). then open the .android folder and delete the cache folder and ddms.cfg and run Eclipse. If your problem is not resolved, follow these steps.

• If your problem is not resolved using the above method, go to the workspace folder and delete it as suggested in this Answer .

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

• If the problem is still not resolved, then pray to God.