JDK-8369692 : JFR: Don't record thread metadata in case jdk.ThreadStart is disabled
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: jfr
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2025-10-13
  • Updated: 2025-11-21
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.
Other
tbdUnresolved
Related Reports
Relates :  
Description
By default, the jdk.ThreadStart event is enabled, which means the thread will be included in the recording. Emitting a checkpoint when a thread starts is therefore fine. If jdk.ThreadStart is disabled, an unnecessary checkpoint is written, which adds waste to the recording.

If this is fixed, the following two lines could be added to test/jdk/jfr/jvm/TestWaste.java

            // Unused threads should not create unreasonable amount of waste
            r.disable("jdk.ThreadStart");
            r.disable("jdk.ThreadStop");
Comments
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/28222 Date: 2025-11-10 18:52:31 +0000
10-11-2025

TestWaste.java currently failing with https://bugs.openjdk.org/browse/JDK-8369949
04-11-2025