Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 484303

Summary:	uinavigator throws org.eclipse.core.runtime.AssertionFailedException: assertion failed: working set with same name already registered
Product:	[Eclipse Project] Platform	Reporter:	Darshana Balakrishnan <bdarshan>
Component:	UI	Assignee:	Platform-UI-Inbox <Platform-UI-Inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	karsten.thoms
Version:	4.5
Target Milestone:	---
Hardware:	PC
OS:	Windows Server 2008
See Also:	https://bugs.eclipse.org/bugs/show_bug.cgi?id=536619
Whiteboard:	stalebug

Description Darshana Balakrishnan

2015-12-14 06:49:52 EST

While testing with the java version mentioned below an exception was found.
java version '1.7.0'
Java(TM) SE Runtime Environment (build pap3270_27sr4-20151127_01(SR4))
IBM J9 VM (build 2.7, JRE 1.7.0 AIX ppc-32 20151126_278956 (JIT enabled, AOT enabled)
J9VM - R27_jvm.27_20151126_0001_B278956
JIT  - tr.r13.java_20151119_105827
GC   - R27_jvm.27_20151126_0001_B278956
J9CL - 20151126_278956)
JCL - 20151118_01 based on Oracle jdk7u91-b15

Stack Trace:
org.eclipse.core.runtime.AssertionFailedException: assertion failed: working set with same name already registered

at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)

at org.eclipse.ui.internal.AbstractWorkingSetManager.addWorkingSet(AbstractWorkingSetManager.java:249)

at org.eclipse.ui.internal.WorkingSetManager.addWorkingSet(WorkingSetManager.java:68)

at org.eclipse.ui.tests.navigator.WorkingSetTest.testDeletedAndRecreated(WorkingSetTest.java:287)

at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:657)

at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:310)

at org.eclipse.test.UITestApplication$2.run(UITestApplication.java:197)

at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)

at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)

at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)

at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)

at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)

at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)

at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)

at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)

at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:140)

at org.eclipse.test.UITestApplication.run(UITestApplication.java:62)

at org.eclipse.test.UITestApplication.start(UITestApplication.java:212)

at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)

at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)

at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)

at org.eclipse.equinox.launcher.Main.run(Main.java:1465)

at org.eclipse.equinox.launcher.Main.main(Main.java:1438)

at org.eclipse.core.launcher.Main.main(Main.java:34)

at com.ibm.svt.eclipse.EclipseRunner.main(EclipseRunner.java:147)

Comment 1 Eclipse Genie

2019-10-06 16:27:42 EDT

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.

--
The automated Eclipse Genie.