Community
Participate
Working Groups
* install the Luna RC1 Java package * open an untitled text file using ctrl+3 * drag the editor out of the window to detach it * drag it back in to split the editor area in 2 (one part will have the editor and the other will be blank) * double click the editor tab to maximize it * click the "shared area" icon in the trim * Eclipse freezes and never comes back
Here's a thread dump caputured with jconsole. It seems to be stuck between lines 997 and 1005 of showStack and it's using all the CPU it can get. No other threads look seem to be involved. Name: main State: RUNNABLE Total blocked: 15 Total waited: 11 Stack trace: org.eclipse.e4.ui.workbench.addons.minmax.TrimStack.showStack(TrimStack.java:1005) org.eclipse.e4.ui.workbench.addons.minmax.TrimStack$9.widgetSelected(TrimStack.java:509) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1152) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1033) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:379) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) org.eclipse.equinox.launcher.Main.run(Main.java:1465)
Interesting...this does require that there has been at least one editor opened due to a different bug; until the first editor opens the Marea's 'selectedElement' is *null* (even though it has the empty stack visible inside it... Easier steps to reproduce: Open an editor, close it maximize a view stack Open the Editor Area from the trim The bug is that the loop that tried to find a part to activate is malformed. It checks for "curContainer.getSelectedElement() instanceof <xxx>" in order to update the loop parameters but of course if 'getSelectedElement()' returns null then none of the tests pass and we loop endlessly. This is a recent regression I think that we might look at for RC4... Here's the Gerrit patch: https://git.eclipse.org/r/27540
+1 for RC4.
+1 for RC4. PW
Submitted with http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?id=d8d3d023889190c877203a9c5033fa28f2004d3b
Verified in I20140603-2300.