-
Bug
-
Resolution: Fixed
-
P3
-
9
-
b109
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.
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.
- relates to
-
JDK-8150163 JarFileSystem support for MRJARs should use the JDK specific Version API
-
- Resolved
-