Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358950 - InvalidRegistryObjectException in Compute launch button tooltip
Summary: InvalidRegistryObjectException in Compute launch button tooltip
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-26 14:08 EDT by Ed Willink CLA
Modified: 2019-11-14 03:53 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2011-09-26 14:08:51 EDT
On 4.2M2.

I was trying to isolate a repro for bug 342294 but once I put the launch config
in the project I got this stack trace of Bug 310756.

When I closed Eclipse ran the launch config, then eveery time I try to access the Run menu I get.

org.eclipse.core.runtime.InvalidRegistryObjectException: Invalid registry object
	at org.eclipse.core.internal.registry.RegistryObjectManager.basicGetObject(RegistryObjectManager.java:272)
	at org.eclipse.core.internal.registry.RegistryObjectManager.getObject(RegistryObjectManager.java:262)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.getConfigurationElement(ConfigurationElementHandle.java:26)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.getContributor(ConfigurationElementHandle.java:134)
	at org.eclipse.debug.internal.core.LaunchConfigurationType.getPluginIdentifier(LaunchConfigurationType.java:299)
	at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTypeContribution.getPluginId(LaunchConfigurationTypeContribution.java:45)
	at org.eclipse.ui.activities.WorkbenchActivityHelper.createUnifiedId(WorkbenchActivityHelper.java:180)
	at org.eclipse.ui.activities.WorkbenchActivityHelper.filterItem(WorkbenchActivityHelper.java:219)
	at org.eclipse.debug.internal.ui.launchConfigurations.LaunchHistory.getCompleteLaunchHistory(LaunchHistory.java:235)
	at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationManager.getFilteredLastLaunch(LaunchConfigurationManager.java:362)
	at org.eclipse.debug.internal.ui.contextlaunching.LaunchingResourceManager.computeLabels(LaunchingResourceManager.java:243)
	at org.eclipse.debug.internal.ui.contextlaunching.LaunchingResourceManager$2.run(LaunchingResourceManager.java:138)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Comment 1 Ed Willink CLA 2011-09-26 14:21:41 EDT
Another probably closely related stack trace from the same config

Root exception:
org.eclipse.core.runtime.InvalidRegistryObjectException: Invalid registry object
	at org.eclipse.core.internal.registry.RegistryObjectManager.basicGetObject(RegistryObjectManager.java:272)
	at org.eclipse.core.internal.registry.RegistryObjectManager.getObject(RegistryObjectManager.java:262)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.getConfigurationElement(ConfigurationElementHandle.java:26)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.getAttribute(ConfigurationElementHandle.java:34)
	at org.eclipse.debug.internal.core.LaunchConfigurationType.getIdentifier(LaunchConfigurationType.java:285)
	at org.eclipse.debug.internal.core.LaunchManager.persistPreferredLaunchDelegate(LaunchManager.java:2373)
	at org.eclipse.debug.internal.core.LaunchManager.persistPreferredLaunchDelegates(LaunchManager.java:2362)
	at org.eclipse.debug.internal.core.LaunchManager.shutdown(LaunchManager.java:2348)
	at org.eclipse.debug.core.DebugPlugin.stop(DebugPlugin.java:630)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764)
	at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:566)
	at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1207)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:592)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257)
	at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215)
	at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284)
	at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:693)
	at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:600)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:390)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:198)
Comment 2 Olivier Thomann CLA 2011-09-26 15:01:56 EDT
Move to Platform/Runtime
Comment 3 Lars Vogel CLA 2019-11-14 03:53:32 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.