JDK-6892138 : Windows GDI platform font lookup apis affect start-up for small UI apps
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2009-10-15
  • Updated: 2013-11-01
  • Resolved: 2011-05-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.
JDK 6 JDK 7
6u18Fixed 7 b128Fixed
Related Reports
Relates :  
JDK-6901159 - LOCALE:[ja_JP] No font has the following family name:[Arial Black] just in 6u18b04
Description
Its aking about 50ms to locate "Tahoma" because of the time taken mostly
in platform APIs and the windows registry. This is WAY better than JDK 1.5
was but we can do better in some known common cases.
Comments
EVALUATION For the most common UI fonts, if we hard code the locations, we can bypass windows APIs until a less common font is used.
15-10-2009