8358679: [asan] vmTestbase/nsk/jvmti tests show memory issues #26176
+21
−10
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.
The fix updates several tests ASAN complains about.
Tests for RawMonitors intentionally passes bad pointer to tested function, they should not be run with ASAN.
Test vmTestbase/nsk/jvmti/scenarios/events/EM07/em07t002 verifies COMPILED_METHOD_LOAD/COMPILED_METHOD_UNLOAD event and uses RawMonitor for synchronization. It destroys the monitor, but some events may arrive later (before VM exits). Usually JVMTI tests do not destroy synchronization monitors, removed destruction here.
Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26176/head:pull/26176
$ git checkout pull/26176
Update a local copy of the PR:
$ git checkout pull/26176
$ git pull https://git.openjdk.org/jdk.git pull/26176/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26176
View PR using the GUI difftool:
$ git pr show -t 26176
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26176.diff
Using Webrev
Link to Webrev Comment