JDK-8199518 : test/hotspot/jtreg/runtime/SelectionResolution tests take a lot longer to run with fastdebug after JDK-8198423
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2018-03-13
  • Updated: 2020-09-01
  • Resolved: 2018-03-13
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 11
11 b07Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Description
Before JDK-8198423:
jib > TEST: runtime/SelectionResolution/InvokeVirtualSuccessTest.java
jib >   build: 2.661 seconds
jib >   compile: 2.66 seconds
jib >   main: 159.982 seconds
jib > TEST RESULT: Passed. Execution successful

After:
jib > TEST: runtime/SelectionResolution/InvokeVirtualSuccessTest.java
jib >   build: 2.166 seconds
jib >   compile: 2.165 seconds
jib >   main: 2766.289 seconds
jib > TEST RESULT: Passed. Execution successful

The slowdown doesn't seem to happen when running with a product build. 
Comments
I posted a patch for RFR on hotspot-runtime.
13-03-2018

Yeah, verifications in metaspace.cpp are too aggressive. I'll tone them down for now and will later check if there is a better option for setting the metaspace verification level (maybe a diagnostic option instead of a simple compile time bool)
13-03-2018

I'm working on a fix right now. Will hopefully soon have a patch.
13-03-2018

We should look at either backing the change out or putting all of the runtime/SelectionResolution tests on the ProblemList until this has been resolved.
13-03-2018