Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Outline view loses its context menu #2050

lwrage opened this issue Nov 8, 2019 · 4 comments


Copy link

@lwrage lwrage commented Nov 8, 2019


Every once in a while the context menu in the outline view disappears. It appears again after a restart.

Steps to Reproduce

  1. Close all editors
  2. Open an AADL file, say P.aadl. -> The context menu in the outline view works.
  3. Open another AADL file, say Q.aadl, leaving P.aadl open. -> The context menu in the outline view works.
  4. Switch to the editor tab for P.aadl. -> The context menu does not appear any more.


Close and reopen the text editor. Only the outline view for editor opened last will work.


  • OSATE Version: 2.6.0
  • Operating System: all

This comment has been minimized.

Copy link

@jjhugues jjhugues commented Nov 8, 2019

I have a workspace that also exhibits this weird behavior
Closing the outline and reopening it restores it

Interesting enough, this bug (in my case) is on a per-AADL package basis. In a given workspace, some packages have this bug, others do not.

Also, I do have occurrences of the menu being partially complete, the missing parts being resolute menus

right click leads to the following stack trace

at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerShowProcessor.showPopup(
at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerShowProcessor.menuAboutToShow(
at org.eclipse.jface.internal.MenuManagerEventHelper.showEventPreHelper(
at org.eclipse.jface.action.MenuManager.handleAboutToShow(
at org.eclipse.jface.action.MenuManager.access$1(
at org.eclipse.jface.action.MenuManager$2.menuShown(
at org.eclipse.swt.widgets.TypedListener.handleEvent(
at org.eclipse.swt.widgets.EventTable.sendEvent(
at org.eclipse.swt.widgets.Display.sendEvent(
at org.eclipse.swt.widgets.Widget.sendEvent(
at org.eclipse.swt.widgets.Widget.sendEvent(
at org.eclipse.swt.widgets.Widget.sendEvent(
at org.eclipse.swt.widgets.Menu.menuWillOpen(
at org.eclipse.swt.widgets.Display.windowProc(
at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
at org.eclipse.swt.internal.cocoa.NSMenu.popUpContextMenu(
at org.eclipse.swt.widgets.Menu._setVisible(
at org.eclipse.swt.widgets.Display.runPopups(
at org.eclipse.swt.widgets.Display.readAndDispatch(
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$
at org.eclipse.core.databinding.observable.Realm.runWithDefault(
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(
at org.eclipse.ui.internal.Workbench.lambda$3(
at org.eclipse.core.databinding.observable.Realm.runWithDefault(
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(
at org.eclipse.ui.internal.ide.application.IDEApplication.start(
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at org.eclipse.equinox.launcher.Main.invokeFramework(
at org.eclipse.equinox.launcher.Main.basicRun(


This comment has been minimized.

Copy link
Contributor Author

@lwrage lwrage commented Nov 8, 2019

This is not an OSATE issue as it happens for Xtend files, too.


This comment has been minimized.

Copy link

@joeseibel joeseibel commented Nov 8, 2019


This comment has been minimized.

Copy link
Contributor Author

@lwrage lwrage commented Nov 10, 2019

Looks like it will be fixed as soon as we upgrade to the next eclipse version.

@lwrage lwrage removed this from the 2.6.1 milestone Nov 12, 2019
@lwrage lwrage closed this Nov 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.