Eclipse崩溃后无法启动的问题解决

一次Eclipse发生内存溢出（ADT环境，多打开几个xml文件内存占用就会飚升），强制结束任务，再次启动Eclipse发现闪退。查看workspace/.metadata/.log文件发现如下错误信息：

!ENTRY org.eclipse.equinox.p2.ui.sdk.scheduler 4 0 2015-04-07 22:29:38.086
!MESSAGE Unable to execute early startup code for an extension
!STACK 1
org.eclipse.core.runtime.CoreException: Plug-in "org.eclipse.equinox.p2.ui.sdk.scheduler" was unable to instantiate class "org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdateScheduler".
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:186)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:273)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52)
at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:269)
at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:117)
at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.Workbench$54.run(Workbench.java:2412)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.lang.NullPointerException
at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdateScheduler.<init>(AutomaticUpdateScheduler.java:68)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
... 11 more
!SUBENTRY 1 org.eclipse.equinox.registry 4 1 2015-04-07 22:29:38.086
!MESSAGE Plug-in "org.eclipse.equinox.p2.ui.sdk.scheduler" was unable to instantiate class "org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdateScheduler".
!STACK 0
java.lang.NullPointerException
at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdateScheduler.<init>(AutomaticUpdateScheduler.java:68)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:273)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52)
at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:269)
at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:117)
at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.Workbench$54.run(Workbench.java:2412)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

解决方法是删除workspace/.metadata/.plugins/目录下的org.eclipse.equinox.p2.ui和org.eclipse.e4.workbench这两个文件夹，之后启动Eclipse恢复正常。

参考链接

时间： 2024-08-07 00:08:55

Eclipse崩溃后无法启动的问题解决的相关文章

NVIDIA Jetson TX2 通过JetPack 3.1刷机后不能启动连网问题解决

Mark一个Jetson TX2刷机后不能启动的问题. 问题的现象是Jetson TX2 通过JetPack 3.1更新固件成功,但是reboot后没有显示,也没有eth0的网络连接,主机控制台卡在"Determing the IP address of target...",如图1所示,手动复位还是这样,以至于主机的JetPack 3.1不能完成后续的步骤. 问题的原因是Jetson TX2连接显示器的HDMI-VGA适配器不被启动时的linux识别,导致卡在检测显示适配器这一步,如

Eclipse配置tomcat后，启动tomcat，访问tomcat报404错误

当你在Eclipse中新建一个工程,配置好tomcat,然后测试tomcat是否配置成功的时候,报404错误异常. 解决方法: 1,把工程文件删除,重新建立一个新的工程, 2,新建一个工程. 3,New 一个 Server ,配置tomcat. 4,双击 弹出配置页面 在Server Locations配置中选择第二个选项,use tomcat installation ,保存,重新启动Tomcat服务,访问成功 注意: 上面不能进行选择,是置灰的,原因是我在这个服务器上启动过这个项目,只有刚新

Eclipse启动 org.eclipse.swt.SWTException: Invalid thread access问题解决方法

最近使用eclipse的时候,当选择完workspace之后,eclipse开始加载启动,在这个阶段经常出现闪退出的情况. 看到日志文件提示一下内容: org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:4441) at org.eclipse.swt.SWT.error(SWT.java:4356) at org.eclipse.swt.SWT.error(SWT.j

Apache连接PHP后无法启动问题解决思路

问题:apache之前正常,连接配置完PHP后无法启动,用apache Test Configration测试后报错形式为: Cannot load D:/php/php5apache2_2.dll into server(或者php5apache2_4.dll) 我个人的解决轨迹是这样的: 1 先查看一下配置时的路径,拼写是否有误,没找出错 2 之前用apache一直没有问题,所以觉得是PHP下载的版本不对,我一开始下载的是5.6,里边的模块文件是php5apache2_4.dll,所以认为P

Openfire3.8.2在eclipse中Debug方式启动最简单的方式

一.前言 最近打算研究一下Openfire,于是打算最好能够以Debug方式启动Openfire的Server,到网上一搜,还果真早到官网的一篇文章来: http://community.igniterealtime.org/docs/DOC-1020 网上很多朋友按照这个教程去搭建,有的说文章有瑕疵的地方,姑且不说瑕疵,就这很长的步骤令人厌恶.本来我想按照这个教程去做,但是,单使用 Eclpse SVN下载令人崩溃,一直显示进度为0%,后来换了TortoiseSVN好一些,下载了两次,每次都花

eclipse Server 没有成功启动

Eclipse3.x中热部署项目 [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.j2ee.server:t' did not find a matching property. F:/myproject/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpweba

Eclipse使用异常——tomcat启动

Eclipse使用异常--tomcat启动 一:问题描述 Eclipse刚上手.很多地方与Myeclipse不一样的地方.比如tomcat的使用.真心的蛋疼. 环境:JDK7.TOMCAT7.Eclipse中从svn检出来的Web项目.将项目部署到tomcat中(不管是哪种方式).最后启动.卡在Starting Apache Tomcat - 就死.过一会后面就提示失败.仅仅弹出如图对话框.没有任何其他信息: 将项目打成war包放在tomcat下直接启动tomcat反而可以正常启动. 二:问题解

Go -- 通过GOTRACEBACK生成程序崩溃后core文件的方法(gcore gdb)

写一个错误的c程序 package dlsym import "testing" func Test_intercept(t *testing.T) { Intercept("gethostbyname\x00") } package dlsym // #cgo CFLAGS: -I. // #include <stddef.h> // #include "dlsym_wrapper.h" import "C" i

Eclipse中的tomcat启动完成之后tomcat还一直提示启动中

在eclipse中,将项目发布到tomcat启动之后,控制台打印处理的日志显示启动已经完成了.但是右下角下面还是一直提示 并且在超过tomcat设置的启动时间之后,就会报错. 百思不得其解.后来在网上看到一个说的是由于启动了代理proxifier的原因.对照着我本地看下,本地虽然没有启动这个代理,但是启动了这个Cisco VPN, 对,就是它,断开VPN连接之后,eclipse中的右下角的"Starting Tomcat v6.0"立即消失的无影无踪. 好吧,貌似一直启动的问题解决了,