[lainhart]

There’s a JSDT bug that I and others have run into, documented here (stack below): https://bugs.eclipse.org/bugs/show_bug.cgi?id=540227

Basically the (evidently) JSDT gets into a state where selecting any view raises an NPE dialog with the stack below, and the only way to get rid of it is to restart the IDE. It looks like the latest version of MyEclipse has also taken this on. With your JS integration, and the fact that the JSDT seems to be getting little love these days, I’m wondering if you folks can somehow work around it.

eclipse.buildId=16.0.0.CI-004
java.version=11.0.2
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -showLocation
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -data file:/C:/eclipseWorkspaces/JiraRD.MyEclipse/ -showLocation

org.eclipse.ui.workbench
Error
Mon Apr 15 15:42:38 EDT 2019
Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".

java.lang.NullPointerException
	at org.eclipse.wst.jsdt.internal.ui.text.java.hover.JavaInformationProvider.update(JavaInformationProvider.java:132)
	at org.eclipse.wst.jsdt.internal.ui.text.java.hover.JavaInformationProvider$EditorWatcher.partActivated(JavaInformationProvider.java:92)
	at org.eclipse.ui.internal.PartService$1.run(PartService.java:86)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
	at org.eclipse.ui.internal.PartService.partActivated(PartService.java:83)
	at org.eclipse.ui.internal.WorkbenchWindow$WWinPartService.partActivated(WorkbenchWindow.java:3081)
	at org.eclipse.ui.internal.WorkbenchPage$3.run(WorkbenchPage.java:5074)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
	at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:5071)
	at org.eclipse.ui.internal.WorkbenchPage.access$3(WorkbenchPage.java:5056)
	at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:214)
	at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:253)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
	at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:250)
	at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:775)
	at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:684)
	at org.eclipse.e4.ui.internal.workbench.swt.AbstractPartRenderer.activate(AbstractPartRenderer.java:97)
	at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.lambda$3(StackRenderer.java:1059)
	at org.eclipse.swt.events.SelectionListener$1.widgetSelected(SelectionListener.java:84)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:252)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4131)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1055)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1064)
	at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:778)
	at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3194)
	at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1877)
	at org.eclipse.swt.custom.CTabFolder.lambda$0(CTabFolder.java:331)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4131)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1055)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3944)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3547)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:636)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1474)

[Brian Fernandes]

Sorry to hear that – that must be a frustrating experience. We’ve been unable to reproduce this issue, can you help with steps or does it occur at random? I’m sure we’ll be able to track it down and fix it in MyEclipse.

As an alternative – if you do a fair amount of JavaScript development, you could install CodeMix (free for MyEclipse Pro and higher customers) which will give you superior JavaScript development capabilities and it might actually fix this error as well. Would that be something you and your team would consider doing? To clarify, we would still fix the issue in the JSDT too.

[lainhart]

Hi Brian –

Thanks for the prompt response. It is difficult to reproduce, although it happens frequently, as described by the bug. I did install CodeMix, and I see the same symptoms.

I’ll see if I can narrow down some steps/environ to repro and update this bug. On your end, maybe there’s a clue in the line number given in the stack trace? Grabbing the NPE, and then maybe spitting a warning would be preferred, but I don’t have the source in front of me to know if that’s a realistic option.

Thanks again — Todd

[Brian Fernandes]

Todd,

The stacktrace definitely helps a great deal, but it’s always good to know how it can be replicated in “real life” – sometimes this is immensely useful, sometimes the code is obvious (our team will know shortly).

If you happen to find a reproducible case, please let us know, but the stack trace is enough for us to start working towards a fix right now.

Thanks!

[Author]

Posts