JDK-8151140 : Replace use of lambda/method ref in jdk.Version constructor
  • Type: Bug
  • Component: core-libs
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2016-03-03
  • Updated: 2016-03-10
  • Resolved: 2016-03-03
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 9
9 b109Fixed
Related Reports
Relates :  
JDK-8150163 - JarFileSystem support for MRJARs should use the JDK specific Version API
Description
Since JDK-8150163, jdk.Version can now be used earlier in startup, but not always. It was noticed that the use of
lambda / method ref in the constructor, in some cases, was the first usage of such, and incurred the initialization costs
of the java.lang.invoke infrastructure ( which can take a significant amount of time on first access).

The solution is to simple avoid the usage, as has been done in other "core" areas, that may be used early in startup.