Bug 218894

Summary: webstart sometimes crashes at shutdown
Product: [Eclipse Project] Platform Reporter: Grant Gayed <grant_gayed>
Component: SWTAssignee: Silenio Quarti <Silenio_Quarti>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: Silenio_Quarti, steve_northover
Version: 3.4   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:
Attachments:
Description Flags
dump
none
controlexample none

Description Grant Gayed CLA 2008-02-13 17:58:29 EST 
Created attachment 89695 [details]
dump

using swt 3.4M5 on OSX 10.5.1 (x86)

Using the fix described in bug 63306, swt apps can now be deployed via JWS on Leopard.  However when closing the deployed app I sometimes get the attached error.  With a very small test case the error happens approximately 25% of the time, but with a larger test case (the SWT ControlExample) it's more frequent than this.

I'm initially giving this to Scott since he fixed bug 63306, and swt is not too conspicuous in the attached error.  CC'ing SSQ in case there is something for swt to do here.
Comment 1 Grant Gayed CLA 2008-02-13 18:04:13 EST 
Created attachment 89697 [details]
controlexample

Here is the Control Example.  The only change that should be needed on your end is to adjust the codebase value in controlexample.jnlp.
Comment 2 Scott Kovatch CLA 2008-02-13 20:23:09 EST 
The crash in callback() is a known problem, and I know Silenio fixed it. As I recall, the SWT wasn't checking to see if it owned the window before attempting to use the window. It's not Web Start-specific.
Comment 3 Silenio Quarti CLA 2008-02-15 11:08:13 EST 
This is similar to bug#202671, but it is a new one since it is happening in 3.4M5.

A callback is coming in after we disposed the callback object.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:11:45 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.