8355069: Allocation::check_out_of_memory() should support CheckUnhandledOops mode

[lmesnik]

The
CheckUnhandledOops
cause failure if JvmtiExport::post_resource_exhausted(...)
is called in
MemAllocator::Allocation::check_out_of_memory()
The obj is null so it is not a real bug.

I am fixing it to reduce noise for CheckUnhandledOops mode for jvmti tests execution.
The vmTestbase/nsk/jvmti/ResourceExhausted/resexhausted002/TestDescription.java
failed with -XX:+CheckUnhandledOops

If define are unwelcome here, the
PreserveObj obj_h(_thread, _obj_ptr);
might be added instead with comment why it is needed for null obj.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8355069: Allocation::check_out_of_memory() should support CheckUnhandledOops mode (Bug - P4)

Reviewers

• Serguei Spitsyn (@sspitsyn - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24766/head:pull/24766
$ git checkout pull/24766

Update a local copy of the PR:
$ git checkout pull/24766
$ git pull https://git.openjdk.org/jdk.git pull/24766/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 24766

View PR using the GUI difftool:
$ git pr show -t 24766

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24766.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back lmesnik! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@lmesnik This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8355069: Allocation::check_out_of_memory() should support CheckUnhandledOops mode

Reviewed-by: sspitsyn

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 63 new commits pushed to the master branch:

• 8c89fb9: 8355179: Reinstate javax/swing/JScrollBar/4865918/bug4865918.java headful and macos run
• bc518a6: 8355240: Remove unused Import in StringUTF16
• a8c6ff1: 8355239: RISC-V: Do not support subword scatter store
• ... and 60 more: https://git.openjdk.org/jdk/compare/22e8a97a1ce4e1c781fbc6f1e271c477fe95f069...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@lmesnik The following label will be automatically applied to this pull request:

• hotspot-gc

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 01: Full - Incremental (cb2904d7)
• 00: Full (aa84af52)

[lmesnik]

/cc hotspot-runtime

[openjdk]

@lmesnik
The hotspot-runtime label was successfully added.

[lmesnik]

/cc serviceability

[openjdk]

@lmesnik
The serviceability label was successfully added.

[sspitsyn]

Looks okay to me.

[lmesnik]

/integrate

[openjdk]

Going to push as commit 83d0bd8.
Since your change was applied there have been 191 commits pushed to the master branch:

• 1652948: 8355442: Reference field lambda forms with type casts are not generated
• 5e27547: 8355789: GenShen: assert(_degen_point == ShenandoahGC::_degenerated_unset) failed: Should not be set yet: Outside of Cycle
• 6850757: 8355689: Wrong native entry name for FloatMaxVector vector math stubs with -XX:MaxVectorSize=8
• ... and 188 more: https://git.openjdk.org/jdk/compare/22e8a97a1ce4e1c781fbc6f1e271c477fe95f069...master

Your commit was automatically rebased without conflicts.

[openjdk]

@lmesnik Pushed as commit 83d0bd8.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.