JDK-8325532 : serviceability/dcmd/compiler/PerfMapTest.java leaves created files in the /tmp dir.
  • Type: Bug
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 23
  • Priority: P5
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2024-02-09
  • Updated: 2024-02-29
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
23Unresolved
Related Reports
Relates :  
JDK-8327054 - DiagnosticCommand Compiler.perfmap does not log on output()
Relates :  
JDK-8314029 - Add file name parameter to Compiler.perfmap
Relates :  
JDK-8323546 - Cleanup jcmd docs for Compiler.perfmap and VM.cds filename parameter
Description
PerfMapTest.java issues the Compiler.perfmap jcmd with a filename argument to write the perfmap to. It does this in 3 different modes. 2 of the modes result in a perfmap file being left in the tmp directory that is not removed after the test executes (and should be removed). The 3rd mode creates the perfmap file in the directory specified by the test.dir property, and is ok to leave the file there.
Comments
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/17992 Date: 2024-02-23 21:55:15 +0000
27-02-2024