8353950: Clipboard interaction on Windows is unstable

[matthiasblaesing]

---

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

Issues

• JDK-8353950: Clipboard interaction on Windows is unstable (Bug - P4)
• JDK-8332271: Reading data from the clipboard from multiple threads crashes the JVM (Bug - P3)

Reviewers

• Phil Race (@prrace - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25897

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

[openjdk]

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

8353950: Clipboard interaction on Windows is unstable
8332271: Reading data from the clipboard from multiple threads crashes the JVM

Reviewed-by: prr

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 4 new commits pushed to the jdk25 branch:

• c832f00: 8359593: JFR: Instrumentation of java.lang.String corrupts recording
• e5ac75a: 8359646: C1 crash in AOTCodeAddressTable::add_C_string
• b79ca5f: 8359248: JFR: Help text for-XX:StartFlightRecording:report-on-exit should explain option can be repeated
• ... and 1 more: https://git.openjdk.org/jdk/compare/cc4e9716acd9339c66176e4181e6444f65873016...jdk25

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. Possible candidates are the reviewers of this PR (@prrace) but any other Committer may sponsor as well.

➡️ 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 issues from the original commit.

[openjdk]

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

• client

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

• 00: Full (1bff35bd)

[matthiasblaesing]

Testing:

• Tests from test/jdk/java/awt/Clipboard were successfully run with fastdebug and release configuration. It was verified, that the new test fails before the change and succeeds afterwards.
• Application level test already done with the original change were repeated and verified