Skip to content

8262915: java.awt.color.ColorSpace.getName() is not thread-safe #2801

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

mrserb
Copy link
Member

@mrserb mrserb commented Mar 3, 2021

The java.awt.color.ColorSpace.getName() method does not use any kind of synchronization to properly initialize and use the static cache for the color components names.


Progress

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

Issue

  • JDK-8262915: java.awt.color.ColorSpace.getName() is not thread-safe

Reviewers

Download

$ git fetch https://git.openjdk.java.net/jdk pull/2801/head:pull/2801
$ git checkout pull/2801

@bridgekeeper
Copy link

bridgekeeper bot commented Mar 3, 2021

👋 Welcome back serb! 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
Copy link

openjdk bot commented Mar 3, 2021

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

  • 2d

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.

@openjdk openjdk bot added the 2d client-libs-dev@openjdk.org label Mar 3, 2021
/**
* Lazy-initialized names of components in the color space.
*/
private transient volatile String [] compName;
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The volatile keyword is the only one necessary to fix this bug, everything else is a cleanup.

@@ -447,60 +451,37 @@ public int getNumComponents() {
/**
* Returns the name of the component given the component index.
*
* @param idx the component index
* @param component the component index
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All other methods use the "component" as a name of the component index.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it will require a CSR request.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nope, it is just renaming of the parameter

if (compName == null) {
switch (type) {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the "switch statement" is replaced by the "switch expression"

@mrserb mrserb marked this pull request as ready for review March 3, 2021 06:04
@openjdk openjdk bot added the rfr Pull request is ready for review label Mar 3, 2021
@mlbridge
Copy link

mlbridge bot commented Mar 3, 2021

Webrevs

@@ -447,60 +451,37 @@ public int getNumComponents() {
/**
* Returns the name of the component given the component index.
*
* @param idx the component index
* @param component the component index
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it will require a CSR request.

@openjdk
Copy link

openjdk bot commented Mar 3, 2021

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

8262915: java.awt.color.ColorSpace.getName() is not thread-safe

Reviewed-by: azvegint, aivanov

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 11 new commits pushed to 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.

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

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Mar 3, 2021
@mrserb
Copy link
Member Author

mrserb commented Mar 3, 2021

/integrate

@openjdk openjdk bot closed this Mar 3, 2021
@openjdk openjdk bot added integrated Pull request has been integrated and removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Mar 3, 2021
@openjdk
Copy link

openjdk bot commented Mar 3, 2021

@mrserb Since your change was applied there have been 11 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

Pushed as commit b397472.

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

@mrserb mrserb deleted the JDK-8262915 branch March 3, 2021 20:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2d client-libs-dev@openjdk.org integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

3 participants