8368781: PerfMemory - make issues more transparent #27602
+67
−64
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.
Currently issues with perfMemory like problems with the secure tmp subdirectory creation are not very transparent in release JVMs.
There exists some warnings traces but they are behind develop flags like Verbose so only available in debug JVMs.
We could (in case of issues) store some information and write it later into hsinfo/hserr files ; or make the existing warnings available too in release JVMs.
Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27602/head:pull/27602
$ git checkout pull/27602
Update a local copy of the PR:
$ git checkout pull/27602
$ git pull https://git.openjdk.org/jdk.git pull/27602/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27602
View PR using the GUI difftool:
$ git pr show -t 27602
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27602.diff
Using Webrev
Link to Webrev Comment