United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6744907 Java WebStart should not create any Swing/AWT objects on warm start
JDK-6744907 : Java WebStart should not create any Swing/AWT objects on warm start

Details
Type:
Enhancement
Submit Date:
2008-09-04
Status:
Closed
Updated Date:
2010-09-17
Project Name:
JDK
Resolved Date:
2009-01-21
Component:
deploy
OS:
generic
Sub-Component:
webstart
CPU:
generic
Priority:
P2
Resolution:
Fixed
Affected Versions:
6
Fixed Versions:
6u12 (b01)

Related Reports
Backport:
Relates:
Relates:

Sub Tasks

Description
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).

                                    

Comments
EVALUATION

Postpone creation of Swing objects until they are actually needed.
                                     
2008-10-16
SUGGESTED FIX

http://sa.sfbay.sun.com/projects/deployment_data/6u12/6744907.1/
                                     
2008-10-30



Hardware and Software, Engineered to Work Together