JDK-6744907 : Java WebStart should not create any Swing/AWT objects on warm start
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 6
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-09-04
  • Updated: 2010-09-17
  • Resolved: 2009-01-21
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.
6u12 b01Fixed 7Fixed
Related Reports
Relates :  
Relates :  
Attempt to start javaws application that has been started recently and was not updated does not 
require any download progress dialogs, security dialogs, etc. 
If nothing is shown on the screen then there is no reason why javaws should trigger initialization of 
Swing/AWT in the javaws secure thread.

Initial experiments using slightly modified refworkload tests show 10+% decrease (30 runs, significant) 
of warm startup time if initialization of UI components does not happen (WinXP).

In more simplistic tests on Vista laptop similar of higher savings are observed too.
Using modified refworkload startup2 test avoiding creation of Swing components 
till they are needed helps to reduce startup time of minimal webstart based swing application by about 13% (from 1662 to 1433 on test WinXP SP2 machine).

SUGGESTED FIX http://sa.sfbay.sun.com/projects/deployment_data/6u12/6744907.1/

EVALUATION Postpone creation of Swing objects until they are actually needed.