Open
Conversation
Tighten JFR emergency dump validation and snapshot handling across the runtime path, including metadata and constant-pool persistence during emergency writes. Add regression coverage for metadata-only and constant-pool dumps so the dumped output stays consistent across those cases.
Validate repository chunk paths before reopening them and keep the stop-recording VM operation preallocated on the runtime side. This also avoids hosted-analysis failures in the recovered-OOM worker test on configurations without JFR support.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary:
This PR adds Native Image JFR emergency-dump support and hardens the runtime for the OOM and recovered-OOM cases exercised by it.
Main changes:
Review guidance:
Original contribution by @roberttoyonaga .