JDK-8293313: NMT: Add "Fake OOM" mode to MallocLimit #10144
Closed
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 RFE adds the optional ability for
-XX:MallocLimit
to, instead of exiting the VM with a fatal error, fake a native OOM on this and all future malloc calls.The user controls this by appending the option "oom" to the malloc limit argument:
That makes it possible to test hotspot robustness in the face of real malloc OOMs, and is the prerequisite for removing the old
MallocMaxTestWords
machinery.Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10144/head:pull/10144
$ git checkout pull/10144
Update a local copy of the PR:
$ git checkout pull/10144
$ git pull https://git.openjdk.org/jdk pull/10144/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10144
View PR using the GUI difftool:
$ git pr show -t 10144
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10144.diff