8294717: (bf) DirectByteBuffer constructor will leak if allocating Deallocator or Cleaner fails with OOME #1396
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.
Clean backport to eliminate a leak corner case.
Additional testing:
tier1 tier2 tier3
Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/1396/head:pull/1396
$ git checkout pull/1396
Update a local copy of the PR:
$ git checkout pull/1396
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/1396/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1396
View PR using the GUI difftool:
$ git pr show -t 1396
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/1396.diff
Webrev
Link to Webrev Comment