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

Bug 318261

Summary: Running IRunnableWithProgress in Wizard crashes IE
Product: [RT] RAP Reporter: Phil Xue <phil.xue>
Component: JFaceAssignee: Project Inbox <rap-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: critical    
Priority: P3 Keywords: needinfo
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
A demo wizard to reproduce the problem none

Description Phil Xue CLA 2010-06-28 19:08:44 EDT
Build Identifier: 1.3.0.20100615-1704

IE7, 8 (possibly 6, but not tested) crashes when running IRunnableWithProgress in Wizard crashes IE with fork being set to true (running in a separate thread) within an event handler in JFace Wizard.

Note that:
1. This issue does not apply to FireFox (tested on FF3)
2. Wizard would not crash if IRunnableWithProgress is running in the current thread (fork = false)

I have created a working sample of Wizard to demonstrate the problem. The wizard can be opened from anywhere using:

new org.eclipse.jface.wizard.WizardDialog(Display.getCurrent().getActiveShell(), new MyWizard()).open();

Reproducible: Always

Steps to Reproduce:
1. Open MyWizard
2. Click button 'Click Me'
3. Click next button or click 'Click Me' button again-> IE crahes (IE8 might restart the tab for crash recovery)
Comment 1 Phil Xue CLA 2010-06-28 19:12:29 EDT
Created attachment 172978 [details]
A demo wizard to reproduce the problem
Comment 2 Ivan Furnadjiev CLA 2010-08-12 08:31:23 EDT
I can't reproduce the crash with your snippet, CVS HEAD and IE8 on Windows 7. Phil, could you test it against CVS HEAD? Could you provide a complete test project/application to demonstrate the problem?
Comment 3 Ivan Furnadjiev CLA 2011-04-21 04:44:44 EDT
I still can't reproduce it. Phil, please reopen this bug if the issue persist and you can provide a complete self-running snippet to reproduce it.
Comment 4 Ivan Furnadjiev CLA 2011-04-21 04:47:44 EDT
This bug sounds to me very similar to bug 332243.