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

Bug 320824

Summary: NPE in ModelServiceImpl.bringToTop
Product: [Eclipse Project] e4 Reporter: Boris Bokowski <bokowski>
Component: UIAssignee: Project Inbox <e4.ui-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: nobody, remy.suen
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:
Attachments:
Description Flags
safe up the call none

Description Boris Bokowski CLA 2010-07-24 16:34:20 EDT 
No steps yet...

Caused by: java.lang.NullPointerException
	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:178)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:86)
	at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:205)
	at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:224)
	at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:408)
	at org.eclipse.e4.ui.internal.workbench.swt.AbstractPartRenderer.activate(AbstractPartRenderer.java:105)
	at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer$ActivationJob.run(StackRenderer.java:113)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
Comment 1 Eric Moffatt CLA 2010-07-24 16:40:35 EDT 
Created attachment 175163 [details]
safe up the call


Do you know how to repro this ?
Comment 2 Boris Bokowski CLA 2010-07-24 16:42:18 EDT 
(In reply to comment #1)
> Do you know how to repro this ?

No, not yet
Comment 3 Boris Bokowski CLA 2010-07-24 16:43:10 EDT 
+1 for the patch.
Comment 4 Eric Moffatt CLA 2010-07-24 17:25:22 EDT 
Committed in >20100725. Applied the patch.

This is likely only fixing the symptom though...shoudl I close it ?
Comment 5 Remy Suen CLA 2010-07-24 22:05:01 EDT 
(In reply to comment #4)
> This is likely only fixing the symptom though...shoudl I close it ?

Well, if we close it then we should make a separate bug to roll it back after 4.0 is out I think.
Comment 6 Dani Megert CLA 2013-06-05 10:56:57 EDT 
Removing outdated target milestone.
Comment 7 Nobody - feel free to take it CLA 2013-06-06 05:46:21 EDT 
The actual code is completely different. No more work can be done on this bug.