JDK-7019614 : Sometimes when cloing the browser after applet is dragged out of browser, applet will also be closed
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2011-02-15
  • Updated: 2011-05-31
  • Resolved: 2011-05-31
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
7 b138Fixed
Related Reports
Relates :  
Relates :  
Tested JRE: b130-pit  http://rehudson.sfbay.sun.com/hudsonws/deploypit/bundles/ Label: b255-2011-02-10_39
Tested OS: winxp
Tested Browser: firefox3.6, IE8

Steps to reproduce:
1) Clear deploment cache 
2) Launch the following applet in browser:
this jnlp applet can be dragged out, and has shortcut hint in jnlp file
3) Drag the applet out of browser
4) Close the browser, if the applet also close, bug is reproduced

Source code location:
Add another applet which can reproduce this bug

SUGGESTED FIX The applet state should be updated once it started to be dragged-out with UI-related operation such as creating shortcut remains until after mouse button is released. Performance issue of AWT events need to be improved, but that should be another CR.

EVALUATION The bug can be reproduced with or without shortcut already installed. The evidence so far shows it could be race condition or some sort of blocking to cause the client VM exit before the drag out action fully completed. Even though the applet looks like it is running outside the browser, the drag process somehow is not completed yet, will need further investigatio to figure out why. According to log files collected for working and exit cases, it is obvious that the client VM exit without "DragHelper sending appletDragFinished" log message, an evidence that the operation is not fully completed or some steps are skipped. DragHelper sending appletDragStarted for applet ID 1 @@@@ drag action started @@@@ @@@@ hello preloader: Stop progressCheck thread DragHelper sending appletDragFinished for applet ID 1 --> missing for failed test @@@@ drag action finished --> missing for failed test