这是它的长短.先短:
>我有一个X Window系统崩溃,导致Eclipse存在不洁净(即,它可能在没有警告的情况下被强制杀死.)
>重新启动eclipse时,它会无限期地挂起“Loading Workbench”.
>删除workspace / .Metadata中的* .snap文件有效,但是午餐后IDE无法正常工作,因为这些文件丢失了.
>删除我的工作区/ .Metadata让eclipse可以正常启动和运行,但……
>当我尝试保存Java文件(任何文件)时,它会无限期挂起“用户 *** 作正在等待” – “构建工作区”
因此,在崩溃之后的某个地方,有一个或多个文件导致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 1org.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.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.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 1org.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.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.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?
解决方法:
我知道你不希望这个作为答案,但我会认真考虑获得另一个Eclipse副本 – 除非你有很多保存的偏好等,你绝对需要坚持.确保将您的工作区复制到其他地方,然后再吹掉破碎的Eclipse版本.
我认为这是节省时间的最佳解决方案.否则你可能会修改设置一段时间,直到你最终得到一个解决方案 – 即使这样你的Eclipse也可能不稳定.
总结以上是内存溢出为你收集整理的android – 如何处理挂在工作区上的Eclipse的持久性问题?全部内容,希望文章能够帮你解决android – 如何处理挂在工作区上的Eclipse的持久性问题?所遇到的程序开发问题。
如果觉得内存溢出网站内容还不错,欢迎将内存溢出网站推荐给程序员好友。
欢迎分享,转载请注明来源:内存溢出
评论列表(0条)