JDK-8193064 : JarFile::getEntry0 method reference use cause for startup regression
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.jar
  • Affected Version: 10
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2017-12-05
  • Updated: 2018-01-10
  • Resolved: 2017-12-05
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 10
10 b35Fixed
Related Reports
Relates :  
JDK-8189611 - JarFile versioned stream and real name support
Description
JDK-8189611 introduced a number of capturing lambdas to implement entry retrieval. Any application that loads classes from a jar file will now initialize a capturing lambda and take a startup regression.

Desugaring this particular use is enough to avoid the majority of the startup regression, but both with an anonymous Function and a lambda it's clear that JDK-8189611 has accidentally regressed code paths that were previously non-allocating.