JDK-7073032 : Should not warmup AWT if FX is requested
- Type: Bug
- Component: deploy
- Sub-Component: deployment_toolkit
- Affected Version: 7-client
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2011-07-30
- Updated: 2013-09-12
- Resolved: 2011-08-17
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.
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.
| JDK 7 | JDK 8 |
|---|---|
7u2 b03Fixed  |
8Fixed |
Description
Both javaws and browser JVM will pass -Dsun.awt.warmup=true to initiate initialization of D3D in a way AWT toolkit can pick it later. That helps to save up to 100ms of startup time but in case of FX this warmup is almost useless (at this moment). We should only request it for for AWT toolkit. If we know we gonna need FX toolkit we should not pass this property