312902 – NPE on shutdown

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

Bug 312902 - NPE on shutdown

Summary: NPE on shutdown

Status:	RESOLVED WORKSFORME

Alias:	None

Product:	e4
Classification:	Eclipse Project
Component:	UI (show other bugs)
Version:	1.0
Hardware:	PC Mac OS X - Carbon (unsup.)

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Project Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2010-05-14 09:24 EDT by Thomas Schindl
Modified:	2010-06-08 10:29 EDT (History)
CC List:	3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Thomas Schindl

2010-05-14 09:24:24 EDT

I sometimes get an NPE when shutdowning my inner e4-Workbench:
--------8<--------
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
Caused by: java.lang.NullPointerException
	at org.eclipse.e4.ui.workbench.swt.internal.AbstractPartRenderer.activate(AbstractPartRenderer.java:136)
	at org.eclipse.e4.workbench.ui.renderers.swt.StackRenderer$ActivationJob.run(StackRenderer.java:86)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
	... 65 more
--------8<--------
I guess this is a timing issue so that the context is already disposed when the UI-Thread sends notifications.

Comment 1 Remy Suen

2010-05-14 09:30:38 EDT

(In reply to comment #0)
> I guess this is a timing issue so that the context is already disposed when the
> UI-Thread sends notifications.

I believe this is caused by the fix for bug 312848. I guess the renderer should ignore activation requests for disposed parts?

Comment 2 Remy Suen

2010-05-14 09:34:39 EDT

(In reply to comment #1)
> I believe this is caused by the fix for bug 312848.

Should be bug 312818.

Comment 3 Thomas Schindl

2010-06-08 10:29:32 EDT

unable to reproduce