I was having the exact same issue. I tried all the workarounds suggested here, including chaging the Projects settings and manually downloading the Android SDKs to no avail. I finally gave up and switched to Intellij IDEA, which works for me.
On Tuesday, June 9, 2009 1:11:03 AM UTC-5, az9702 wrote: > > You may want to try turning off "Projects -> Build Automatically" > > This workaround works in my IDE every time. > > > On Jun 8, 10:02 am, Jakob Sachse <[email protected]> wrote: > > I am having the same trouble, is there any workaround that tourned out > > to be working? > > > > On 14 Mai, 22:14, "[email protected]" <[email protected]> wrote: > > > > > Stack trace was sent by email. Part of it is shown below. > > > > > Trace was captured on Eclipse start (after turning back on "Projects- > > > > > >Build Automatically") & Android SDK Content Loader stuck at 60%. > > > > > Let us know what you find or send more detailed info on capturing > > > trace dump. > > > > > > ##------------------------------------------------------------------------------------------------------------- > > > > > > > StackTrace Remote Thread" prio=6 tid=0x36afc800 nid=0xfac runnable > > > [0x00000000..0x38a9fa60] > > > java.lang.Thread.State: RUNNABLE > > > > > "Timer-1" prio=6 tid=0x36ed4000 nid=0x12cc in Object.wait() > > > [0x3b69f000..0x3b69fd94] > > > java.lang.Thread.State: TIMED_WAITING (on object monitor) > > > at java.lang.Object.wait(Native Method) > > > - waiting on <0x071a7cd8> (a java.util.TaskQueue) > > > at java.util.TimerThread.mainLoop(Unknown Source) > > > - locked <0x071a7cd8> (a java.util.TaskQueue) > > > at java.util.TimerThread.run(Unknown Source) > > > > > "Worker-46" prio=6 tid=0x36d8d800 nid=0x16c in Object.wait() > > > [0x3b49f000..0x3b49fa94] > > > java.lang.Thread.State: TIMED_WAITING (on object monitor) > > > at java.lang.Object.wait(Native Method) > > > at > org.eclipse.core.internal.jobs.ThreadJob.joinRun(ThreadJob.java: > > > 189) > > > - locked <0x05678bb8> (a java.lang.Object) > > > at org.eclipse.core.internal.jobs.ImplicitJobs.begin > > > (ImplicitJobs.java:87) > > > at org.eclipse.core.internal.jobs.JobManager.beginRule > > > (JobManager.java:230) > > > at org.eclipse.core.internal.resources.WorkManager.checkIn > > > (WorkManager.java:117) > > > at > org.eclipse.core.internal.resources.Workspace.prepareOperation > > > (Workspace.java:1747) > > > at > org.eclipse.core.internal.resources.Workspace.run(Workspace.java: > > > 1795) > > > at > > > > org.eclipse.jdt.internal.core.ProjectReferenceChange.updateProjectReferencesIfNecessary > > > > > (ProjectReferenceChange.java:107) > > > at > > > > org.eclipse.jdt.internal.core.ChangeClasspathOperation.classpathChanged > > > (ChangeClasspathOperation.java:59) > > > at > > > org.eclipse.jdt.internal.core.SetContainerOperation.executeOperation > > > (SetContainerOperation.java:110) > > > at org.eclipse.jdt.internal.core.JavaModelOperation.run > > > (JavaModelOperation.java:716) > > > at > org.eclipse.core.internal.resources.Workspace.run(Workspace.java: > > > 1800) > > > at > org.eclipse.jdt.internal.core.JavaModelOperation.runOperation > > > (JavaModelOperation.java:782) > > > at > org.eclipse.jdt.core.JavaCore.setClasspathContainer(JavaCore.java: > > > 4616) > > > at > > > > com.android.ide.eclipse.adt.project.internal.AndroidClasspathContainerInitializer.updateProjects > > > > > (Unknown Source) > > > at com.android.ide.eclipse.adt.AdtPlugin$13.run(Unknown > Source) > > > - locked <0x0629aef8> (a java.util.ArrayList) > > > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > > > > > On May 14, 8:37 am, Raphael <[email protected]> wrote: > > > > > > On Fri, May 8, 2009 at 11:11 PM, [email protected] <[email protected]> > wrote: > > > > > > > After I switched to SDK 1.5, the Android SDK Content Loader is > stuck > > > > > when Eclipse starts. > > > > > In my case, it is always stuck at 60%. > > > > > > Interesting. Can you help me debug this? I'd like to understand > where > > > > it gets stuck. > > > > > > If you're on Linux, start Eclipse from the command-line. IIRC when > it > > > > gets stuck press Control-C and it will dump a stack trace of all the > > > > threads. > > > > > > In case the Control-C trick doesn't work, e.g. if you're on Windows, > I > > > > successfully used the StackTrace tool fromhttp:// > www.adaptj.com/main/downloadinthepast, it's a web start for > > > > Linux, MacOS and Windows : point it to the Eclipse JVM and it will > > > > create a stack trace of the running threads. > > > > > > Please do that if you can and email me the stack trace privately > (it's > > > > quite long). > > > > > > Thanks in advance > > > > R/ -- -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
