Troubleshoot issues that cannot be started after eclipse crashes

Source: Internet
Author: User

A memory overflow (ADT environment, multiple Open XML files will soar) Once eclipse occurs, forcing the end of the task and starting Eclipse Discovery flashback again. View Workspace/.metadata/.log file found the following error message:

! 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)
... One 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)

The workaround is to delete the workspace/.metadata/.plugins/ Directory under Org.eclipse.equinox.p2.ui and org.eclipse.e4.workbench these two folders, and then start eclipse back to normal.

Reference links

Troubleshoot issues that cannot be started after eclipse crashes

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.