Bugzilla – Full Text Bug Listing
| Summary: | [Workbench][Perspectives] NPE in WorkbenchPage.busyShowView() | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Francis Upton IV <francisu> |
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | kdevolder, remy.suen |
| Version: | 3.6.1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
|
Description
Francis Upton IV
*** Bug 356540 has been marked as a duplicate of this bug. *** I am seeing these in regression tests of STS that run with Eclipse 4.4.RC2 as target platform. build 12-Jun-2014 19:34:16 java.lang.NullPointerException build 12-Jun-2014 19:34:16 at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1273) build 12-Jun-2014 19:34:16 at org.eclipse.ui.internal.WorkbenchPage$13.run(WorkbenchPage.java:4144) build 12-Jun-2014 19:34:16 at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) build 12-Jun-2014 19:34:16 at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4140) build 12-Jun-2014 19:34:16 at org.eclipse.ui.internal.console.ConsoleManager$ShowConsoleViewJob.runInUIThread(ConsoleManager.java:321) build 12-Jun-2014 19:34:16 at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:97) build 12-Jun-2014 19:34:16 at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) build 12-Jun-2014 19:34:16 at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) build 12-Jun-2014 19:34:16 at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806) build 12-Jun-2014 19:34:16 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444) I haven't seen them during 'regular' use of Eclipse 4.4 so I am not sure if they can occur as such or only because of something 'funky' we may be doing in our test harness. The exceptions caused some test failures on our end. So I am dealing with them by catching the NPEs that pop out of calls to 'readAndDispatch' in our test harness and simply logging and ignoring them. If you add an NPE breakpoint when you run the test could you perhaps give us the code that you're executing when the NPE occurs ? That'll help us track it down I think. Not sure what code you'd want me to give you. As far as I can tell the error seems to come from a bit of code posted via a Display.asynchExec call. And as far as I can tell that call probably came from Eclipse code base: org.eclipse.ui.internal.console.ConsoleManager$ShowConsoleViewJob.runInUIThread(ConsoleManager.java:321) Anything that caused this job to be scheduled is really no longer there when the NPE breakpoint gets hit. 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. |