Android Eclipse Hanging

Question

I try to get ADT to work in Eclipse, but I get occasional freezes when the eclipse simply blocks for no apparent reason, usually requiring "killall java" to properly clear it from memory.

I'm on Ubuntu 10.4 (64 bit) Here are the details of installing eclipse / android:

eclipse Version: 3.5.2 Build identifier: M20100211-1343 Android development tools 0.9.8.v201008281755-53891 com.android.ide.eclipse.adt.feature.group Android DDMS 0.9.8.v201008281755-53891 com.android.ide .eclipse.ddms.feature.group

Here's the output from java -version: java version "1.6.0_20" Java (TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot (TM) 64-bit server VM (build 16.3-b01, mixed mode)

I often don’t get anything in workspace logs, but here is an example of what came after Eclipse hung just now:! ENTRY org.eclipse.core.resources 8 2 2010-09-21 10: 22: 27.407 MESSAGE Problems arise when calling the code from the plug-in: "org.eclipse.core.resources". STACK 1 org.eclipse.core.runtime.CoreException: the project goal has not yet been resolved. at com.android.ide.eclipse.adt.internal.build.BaseBuilder.stopBuild (Unknown source) at com.android.ide.eclipse.adt.internal.build.BaseBuilder.abortOnBadSetup (Unknown source) on com.android.ide .eclipse.adt.internal.build.PreCompilerBuilder.build (Unknown source) at org.eclipse.core.internal.events.BuildManager $ 2.run (BuildManager.java:627) at org.eclipse.core.runtime.SafeRunner.run (SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild (BuildManager.java:170) at org.eclipse.core.internal.events.BuildManager.basicBuild (BuildManager.java:201) at org.eclipse.core.internal.events.BuildManager $ 1.run (BuildManager.java:253) at org.eclipse.core.runtime.SafeRunner.run (SafeRunner.java:42) at org.eclipse.core.internal.events .BuildManager.basicBuild (BuildManager.java:256) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop (BuildManager.java:309) at org.eclipse.core .internal.events.BuildManager.build (BuildManager.javahaps41) at org.eclipse.core.internal.events.AutoBuildJob.doBuild (AutoBuildJob.java:140) at org.eclipse.core.internal.events.AutoBuildJob.run (AutoBuildJob.java:238) at org.eclipse.core.internal.jobs.Worker.run (Worker.java:55) SUBENTRY 1 com.android.ide.eclipse.adt 8 0 2010-09-21 10:22: 27.407! MESSAGE The goal of the project has not yet been achieved. SUBENTRY 1 com.android.ide.eclipse.adt 8 0 2010-09-21 10: 22: 27.407! MESSAGE The goal of the project has not yet been achieved.

There were two of these entries - identical, with the exception of time stamps.

I tried almost every version of eclipse that I can download, I tried to bind adt to sdk 1.6 r1, r2 and r3.

Does anyone have any ideas? I'm here. Eclipse is pretty solid for me using other plugins - C / C ++, PyDev, PHP, the web stuff is working fine, but as soon as I try to use the Android plugin, I start hanging. I turned off code completion, in case it is, but no, no matter what I do, I get a couple of lines printed, then everything turns gray.

Answer 1

I prefer installing eclipse for each programming language / language pack. Java + Android, Php + Web (HTML, JS ...), Python ... Maybe ADT is actually not compatible with one of your installed plugins. Try using a separate installation / instance of eclipse

Answer 2

This happened to me because of damaged Eclipse toolkit. In particular, I saw how Eclipse freezes when loading the com.android.ide.eclipse.adt configuration.

At first I tried to remove com.android.ide.eclipse.adt from my /.metadata/.plugins workspace, but that did not help.

However, removing org.eclipse.ui.workbench from workspace / .metadata / .plugins seems to do the trick.

It seems that the setup of the workplace is somehow damaged. So try these guys:

rm /path_to_workspaces/workspace/.metadata/.plugins/org.eclipse.ui.workbench -fr

It seems that now I fixed this problem, and I believe that it was the same solution that I encountered when I had the same problem 2 years ago (but now found this question on SO)

Answer 3

Recently, this problem continues to grow. I usually solve it

 1. Renaming org.eclipse.core.resources(in your *currently active workspace folder*/.metadata/plugins folder) to something like org.eclipse.core.resources.old 2. Kill eclipse task if it is still hung in memory 3. Start eclipse, it should start fine and create org.eclipse.core.resources again 4. Close eclipse 5. Delete the newly created org.eclipse.core.resources folder and rename org.eclipse.core.resources.old to org.eclipse.core.resources 6. Start eclipse again. 

It worked for me