这是它的长短。首先简短:
因此,在崩溃之后的某个地方,有一个或多个文件导致Eclipse在尝试恢复我正在编辑的文件时挂起,或以其他方式处理我的工作区。以下是我的.log文件中的一些相关例外:
从第2点开始:
!ENTRY org.eclipse.core.resources 2 10035 2011-01-24 11:21:33.870
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
!ENTRY org.eclipse.core.resources 8 2 2011-01-24 11:21:35.040
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 1
org.eclipse.core.runtime.CoreException: SDK is not loaded yet
at com.android.ide.eclipse.adt.internal.build.builders.BaseBuilder.stopBuild(Unknown Source)
at com.android.ide.eclipse.adt.internal.build.builders.BaseBuilder.abortOnBadSetup(Unknown Source)
at com.android.ide.eclipse.adt.internal.build.builders.ResourceManagerBuilder.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.java:341)
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)
从第5点开始:
!ENTRY org.eclipse.core.resources 8 2 2011-01-24 14:14:47.331
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 1
org.eclipse.core.runtime.CoreException: Project target not loaded yet.
at com.android.ide.eclipse.adt.internal.build.builders.BaseBuilder.stopBuild(Unknown Source)
at com.android.ide.eclipse.adt.internal.build.builders.BaseBuilder.abortOnBadSetup(Unknown Source)
at com.android.ide.eclipse.adt.internal.build.builders.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.java:341)
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 2011-01-24 14:14:47.331
!MESSAGE Project target not loaded yet.
!SUBENTRY 1 com.android.ide.eclipse.adt 8 0 2011-01-24 14:14:47.331
!MESSAGE Project target not loaded yet.
此时,我真正想要的是能够在不崩溃的状态下使用Eclipse。任何建议都不能完全删除我的整个〜/ .eclipse目录,我的工作区,并从头开始重新安装Eclipse?
答案 0 :(得分:8)
尝试从<> /。metadata / .plugins / org.eclipse.core.resources /
中删除.snap文件答案 1 :(得分:3)
我知道你不希望这个作为答案,但我会认真考虑获得另一个Eclipse副本 - 除非你有很多保存的偏好等,你绝对需要坚持。确保将您的工作区复制到其他地方,然后再吹掉破碎的Eclipse版本。
我认为这是节省时间的最佳解决方案。否则你可能会修改设置一段时间,直到你最终得到一个解决方案 - 即使这样你的Eclipse也可能不稳定。
答案 2 :(得分:2)
我从文件系统的工作区中删除了一些项目(已经在版本控制中),这似乎解决了这个问题。
答案 3 :(得分:2)
将所有项目从工作区移动到另一个文件夹然后再次启动eclipse,它应该立即开始。启动时,您可以导入或简单地将项目移回工作区。我认为有些项目会让它抛出NullPointerException
。我不知道为什么。
答案 4 :(得分:1)
杀死日食时,您应该从.lock
中移除workspace/.metadata
。它为我做了诀窍。
答案 5 :(得分:0)
今天发生在我身上,经过多次头疼,我重新启动,问题就消失了......
答案 6 :(得分:0)