8358183: [JVMCI] crash accessing nmethod::jvmci_name in CodeCache::aggregate #25608
+3
−0
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.
This change addresses an intermittent crash in CompileBroker::print_heapinfo() when accessing JVMCI metadata after a CodeBlob::purge().
The issue is a regression after:
The change zeroes out _mutable_data_size, _relocation_size, and _metadata_size in purge() so that after purge jvmci_data_size() returns 0 and CompileBroker::print_heapinfo() won’t touch an invalid _metadata.
Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25608/head:pull/25608
$ git checkout pull/25608
Update a local copy of the PR:
$ git checkout pull/25608
$ git pull https://git.openjdk.org/jdk.git pull/25608/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 25608
View PR using the GUI difftool:
$ git pr show -t 25608
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25608.diff
Using Webrev
Link to Webrev Comment