8191278: MappedByteBuffer bulk access memory failures are not handled gracefully

[snazarkin]

I'd like to backport this changes to fix crash happens on memory mapped file operations. The patch applies cleanly.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8191278: MappedByteBuffer bulk access memory failures are not handled gracefully

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk13u-dev pull/240/head:pull/240
$ git checkout pull/240

Update a local copy of the PR:
$ git checkout pull/240
$ git pull https://git.openjdk.java.net/jdk13u-dev pull/240/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 240

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk13u-dev/pull/240.diff

[bridgekeeper]

👋 Welcome back snazarki! 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]

This backport pull request has now been updated with issue and summary from the original commit.

[openjdk]

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

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

8191278: MappedByteBuffer bulk access memory failures are not handled gracefully

Unsafe.copy*Memory access failures are handled gracefully.

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 2 new commits pushed to the master branch:

• 0cac580: 8258373: Update the text handling in the JPasswordField
• 6dd4098: 8257620: Do not use objc_msgSend_stret to get macOS version

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[mlbridge]

Webrevs

• 00: Full (773cbd72)

[snazarkin]

/integrate

[openjdk]

@snazarkin
Your change (at version 773cbd7) is now ready to be sponsored by a Committer.

[yan-too]

/sponsor

[openjdk]

Going to push as commit 40ab2a0.
Since your change was applied there have been 2 commits pushed to the master branch:

• 0cac580: 8258373: Update the text handling in the JPasswordField
• 6dd4098: 8257620: Do not use objc_msgSend_stret to get macOS version

Your commit was automatically rebased without conflicts.

[openjdk]

@yan-too @snazarkin Pushed as commit 40ab2a0.

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