Sorry if I\'m asking this the wrong way (if I am, let me know what I should be doing instead.) The site warned me not to leave this as an answer and I don\'t have enough rep
Another solution is to clean up project-specific meta data directories which are stored under your workspace directory. $ cd workspace/.metadata/.plugins/org.eclipse.core.resources/.projects $ rm -rf *
Restart Eclipse.
This is the solution I found which works correctly:
Make sure that eclipse is not active. If it is active kill eclipse from the processes tab of the task manager
Open %USERPROFILE%/ on Windows or simply ~ on Linux/OS X (You can locate this folder from the Desktop)
Go to .android folder (This may be a hidden folder)
Delete the folder cache which is located inside .android folder
Delete the file ddms.cfg which is located inside .android folder
Start Eclipse
Hope that this will work for you.
Below scenario will work.
Go to your workspace directory \workspace\.metadata\.plugins\org.eclipse.core.resources\\.projects
.projects folder and take backup for temporary..projects folder from workspace directory. (you will not loose your projects).projects folder which you have backup earlier to \workspace\.metadata\.plugins\org.eclipse.core.resources\ directory. Overwrite existing .projects folder.In above scenario Eclipse will automatically finds your projects as earlier. You do not have to import manually.
Working for me.
I myself ran into this issue, and what have I not tried, all the possible stackoverflow links. None helped.
While eclipse is running and showing me the stupid "Android content (killing me:)".I started the task manager , and I saw adb, cmd.exe is running. Killed it. And voila!.
The way that works for me (at least last 2 years):
cd .metadatafind . -name .markers -exec rm {} \;-clean and -refresh keys: In my case run:
/Users/maxim/POC/adt-bundle-mac-x86_64-20140702/eclipse/Eclipse.app/Contents/MacOS/eclipse -clean -refresh
That's all.
After Eclipse will up, wait for full stuff loading and you can restart it if you don't want to see all log output in console.
I closed all open projects before the progress status could get to "Android sdk content loader 0%" and then opened them one by one. Fortunately the problem got resolved.