8364434: Inconsistent BufferedContext state after GC

[YaaZ]

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8364434 needs maintainer approval

Issue

• JDK-8364434: Inconsistent BufferedContext state after GC (Bug - P3 - Approved)

Reviewers

• Alexey Ushakov (@avu - no project role)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 148

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk25u/pull/148.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

@YaaZ 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:

8364434: Inconsistent BufferedContext state after GC

Reviewed-by: avu

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

• cefd945: 8365919: Replace currentTimeMillis with nanoTime in Stresser.java
• 147ed00: 8357064: cds/appcds/ArchiveRelocationTest.java failed with missing expected output
• 304f253: 8362836: JFR: Broken pipe in jdk/jfr/event/io/TestIOTopFrame.java
• ... and 65 more: https://git.openjdk.org/jdk25u/compare/f9713d1587a336e1b4a9b3f29ae90cb388f102d3...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.

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).

[openjdk]

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

[mlbridge]

Webrevs

• 00: Full (9a13ff1b)

[avu]

LGTM

[avu]

/sponsor

[openjdk]

@avu Only Committers are allowed to sponsor changes.