JDK-8257919 : [JVMCI] profiling info didn't change after reprofile
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 11,16,17
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2020-12-08
  • Updated: 2022-02-06
  • Resolved: 2020-12-11
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 JDK 16 JDK 17
11.0.14-oracleFixed 16 b29Fixed 17Fixed
Related Reports
Relates :  
JDK-8252049 - Native memory leak in ciMethodData ctor
Sub Tasks
JDK-8257986 :  
[JVMCI] ProblemList 2 reprofile JVMCI tests - Resolved
Description
Today I noticed that 2 JVMCI tests failed which seems the same way when run with "-ea -esa -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -XX:-TieredCompilation" flags:

compiler/jvmci/compilerToVM/ReprofileTest.java
"profiling info didn't change after reprofile"

compiler/jvmci/compilerToVM/IsMatureVsReprofileTest.java
"Got unexpected isMature state after reprofiling: expected false to equal true"

It could be tests bug.
Comments
Changeset: b1afed75 Author: Vladimir Ivanov <vlivanov@openjdk.org> Date: 2020-12-11 21:50:49 +0000 URL: https://git.openjdk.java.net/jdk16/commit/b1afed75
11-12-2020
Verified locally that after reverting JDK-8252049 changes tests passed.
09-12-2020
Verified locally that after reverting JDK-8252049 changes tests passed.
09-12-2020
Very easy to reproduce by running with '-XX:-TieredCompilation -Xbatch'. Start failing after JDK-8252049: Native memory leak in ciMethodData ctor
09-12-2020
This is making significant noise in the CI so bumping to P2. Please fix or ProblemList.
09-12-2020