| Summary: | SWTException when creating a new extension point | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Ankur Sharma <ankur_sharma> |
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert, dash.alpha, remy.suen |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Ankur Sharma
I've seen what appears to be the same exception trace thrown in Eclipse 3.6 (20100617-1415) when using a Wizard (in a WizardDialog) where I call "getContainer().run(true, true, runnable)" multiple times with different runnables. Sometimes after the 2nd runnable is run in this way, the exception will be thrown; other times it completes normally. (In reply to comment #1) > I've seen what appears to be the same exception trace thrown in Eclipse 3.6 > (20100617-1415) when using a Wizard (in a WizardDialog) where I call > "getContainer().run(true, true, runnable)" multiple times with different > runnables. Sometimes after the 2nd runnable is run in this way, the exception > will be thrown; other times it completes normally. I think it's important to note that the an AccumulatingProgressMonitor is being used (from the stack trace). I suspect that when the monitor does an asyncExec() to update the UI (e.g. in setTaskName()), it's possible that the WizardDialog gets closed before the runnable runs? *** This bug has been marked as a duplicate of bug 401741 *** |