JDK-8330625 : Compilation memory statistic: prevent tearing of the final report
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 21,22,23
  • Priority: P5
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2024-04-19
  • Updated: 2024-04-29
  • Resolved: 2024-04-26
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 23
23 masterFixed
Related Reports
Relates :  
Description
When running with `-XX:CompileCommand=memstat,...,print`, we will print a final report to tty with one line per compiled method and per compiler.

But "print" also activates logging of memory costs after each individual compilation. Compiler threads may still be running and finishing last compilations when the final report is being printed, which causes those log lines to interrupt the final report.

That should be fixed.
Comments
Changeset: 2b7176a5 Author: Thomas Stuefe <stuefe@openjdk.org> Date: 2024-04-26 12:06:57 +0000 URL: https://git.openjdk.org/jdk/commit/2b7176a55ad0e5c6ba34abba3fe8fc1a411a5e2d
26-04-2024

A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/18866 Date: 2024-04-19 13:50:02 +0000
22-04-2024

ILW = Memstat report interleaved with unrelated lines, medium?, no workaround = LMH = P5
19-04-2024