Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368058 - org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63) throws InjectionException (NPE)
Summary: org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:...
Status: CLOSED DUPLICATE of bug 366468
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-06 15:53 EST by Reuben Garrett CLA
Modified: 2012-01-08 07:37 EST (History)
1 user (show)

See Also:


Attachments
Eclipse configuration (861.08 KB, text/plain)
2012-01-06 15:55 EST, Reuben Garrett CLA
no flags Details
Eclipse log with stack traces (984.80 KB, text/plain)
2012-01-06 15:55 EST, Reuben Garrett CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Reuben Garrett CLA 2012-01-06 15:53:33 EST
I occasionally receive a leaked NPE dialog when working in Eclipse.  I believe the exception is provoked by the MercurialEclipse plugin I'm using, which also has some issues (see http://www.javaforge.com/issue/23290).  However, I'm guessing it's not supposed to leak through such that Eclipse throws an unchecked exception, so I'm opening this ticket just to be safe.  Stack trace and config will be attached.  

-- Configuration Details --
Product: Eclipse 1.5.0.20110817-2116 (org.eclipse.epp.package.jee.product)
Installed Features:
 org.eclipse.platform 4.2.0.v20111129-9IF7EHAmFuzFOcSz-MfDWL7uSMPWVz0QZg10z0BYVl6TH
Comment 1 Reuben Garrett CLA 2012-01-06 15:55:36 EST
Created attachment 209151 [details]
Eclipse configuration
Comment 2 Reuben Garrett CLA 2012-01-06 15:55:56 EST
Created attachment 209152 [details]
Eclipse log with stack traces
Comment 3 Remy Suen CLA 2012-01-08 07:37:36 EST

*** This bug has been marked as a duplicate of bug 366468 ***