Community
Participate
Working Groups
From bug 171558: ------- Comment #2 From Pascal Rapicault 2007-02-04 22:13:23 [reply] ------- Using the core tools, I dig a bit further however being not familiar with UI code I can not comment on what I see. However I do think it needs some close look from the experts. First here is the stack trace of what caused the activation of the PDE UI plugin: at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:278) at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227) at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1245) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:147) at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:759) at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51) at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:242) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:238) at org.eclipse.ui.internal.registry.EditorDescriptor.getEditorMatchingStrategy(EditorDescriptor.java:618) at org.eclipse.ui.internal.EditorManager.findEditors(EditorManager.java:478) at org.eclipse.ui.internal.EditorManager.findEditors(EditorManager.java:428) at org.eclipse.ui.internal.EditorManager.findEditor(EditorManager.java:391) at org.eclipse.ui.internal.EditorManager.findEditor(EditorManager.java:373) at org.eclipse.ui.internal.WorkbenchPage.findEditor(WorkbenchPage.java:1914) at org.eclipse.ui.NavigationLocation.getEditorPart(NavigationLocation.java:44) at org.eclipse.ui.NavigationLocation.getText(NavigationLocation.java:60) at org.eclipse.ui.internal.NavigationHistoryEntry.<init>(NavigationHistoryEntry.java:49) at org.eclipse.ui.internal.NavigationHistory.createEntry(NavigationHistory.java:563) at org.eclipse.ui.internal.NavigationHistory.addEntry(NavigationHistory.java:316) at org.eclipse.ui.internal.NavigationHistory.access$9(NavigationHistory.java:300) at org.eclipse.ui.internal.NavigationHistory$2.run(NavigationHistory.java:168)
Mass update - removing 3.4 target. This was one of the bugs I marked for investigation (and potential fixing) in 3.4 but I ran out of time. Please ping on the bug if fixing it would be really important for 3.4, and does not require API changes or feature work.
Remy is now responsible for watching the [EditorMgmt] component area.
The gist of the problem here is described by bug 171558 comment 11. Any plug-in that is contributing an editor matching strategy and has an editor opened in the back (its bundle not originally activated due to our lazy loading strategy) will be instantiated (and subsequently have its bundle activated) during the restoration of the navigation history.
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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie.
