Skip to content
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

8272417: ZGC: fastdebug build crashes when printing ClassLoaderData #5107

Closed
wants to merge 2 commits into from

Conversation

tbzhang
Copy link
Contributor

@tbzhang tbzhang commented Aug 13, 2021

Following test fails on fastdebug build with the options: "-XX:+UseZGC -XX:+VerifyAfterGC -Xlog:gc*=trace". It crashes on the unknown claim value of the ClassLoaderData

public class A {
public static void main(String... args) {
System.gc();
}
}

The unknown claim value of the ClassLoaderData is "ClassLoaderData::_claim_other | ClassLoaderData::_claim_strong" which is introduced by the ZVerifyOopClosure. This patch clears the CLD's claimed marks after the ZGC verification


Progress

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

Issue

  • JDK-8272417: ZGC: fastdebug build crashes when printing ClassLoaderData

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5107/head:pull/5107
$ git checkout pull/5107

Update a local copy of the PR:
$ git checkout pull/5107
$ git pull https://git.openjdk.java.net/jdk pull/5107/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 5107

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5107.diff

@bridgekeeper bridgekeeper bot added the oca Needs verification of OCA signatory status label Aug 13, 2021
@bridgekeeper
Copy link

bridgekeeper bot commented Aug 13, 2021

Hi @tbzhang, welcome to this OpenJDK project and thanks for contributing!

We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed in a comment in this pull request.

If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user tbzhang" as summary for the issue.

If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered in a comment in this pull request.

@tbzhang
Copy link
Contributor Author

tbzhang commented Aug 13, 2021

/covered

@openjdk
Copy link

openjdk bot commented Aug 13, 2021

@tbzhang 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.

@openjdk openjdk bot added the hotspot-gc hotspot-gc-dev@openjdk.org label Aug 13, 2021
@bridgekeeper bridgekeeper bot added the oca-verify Needs verification of OCA signatory status label Aug 13, 2021
@bridgekeeper
Copy link

bridgekeeper bot commented Aug 13, 2021

Thank you! Please allow for a few business days to verify that your employer has signed the OCA. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated!

@robilad
Copy link

robilad commented Aug 17, 2021

Hi, please contact me at Dalibor.Topic@oracle.com so that I can mark your account as verified.

@tbzhang
Copy link
Contributor Author

tbzhang commented Aug 18, 2021

Hi, please contact me at Dalibor.Topic@oracle.com so that I can mark your account as verified.

Thank you!

@bridgekeeper bridgekeeper bot removed oca Needs verification of OCA signatory status oca-verify Needs verification of OCA signatory status labels Aug 19, 2021
@openjdk openjdk bot added the rfr Pull request is ready for review label Aug 19, 2021
@mlbridge
Copy link

mlbridge bot commented Aug 19, 2021

Webrevs

Copy link
Member

@stefank stefank left a comment

Choose a reason for hiding this comment

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

I mentioned in the bug report that this is not enough to correctly fix this bug. Could you fix the printing code instead?

@tbzhang
Copy link
Contributor Author

tbzhang commented Aug 20, 2021

I mentioned in the bug report that this is not enough to correctly fix this bug. Could you fix the printing code instead?

Yes, Thanks for your advice!

Copy link
Member

@stefank stefank left a comment

Choose a reason for hiding this comment

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

Looks good. Thanks.

@openjdk
Copy link

openjdk bot commented Aug 20, 2021

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

8272417: ZGC: fastdebug build crashes when printing ClassLoaderData

Reviewed-by: stefank, pliden

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

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 (@stefank, @pliden) 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 openjdk bot added the ready Pull request is ready to be integrated label Aug 20, 2021
Copy link
Contributor

@pliden pliden left a comment

Choose a reason for hiding this comment

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

Looks good.

@tbzhang
Copy link
Contributor Author

tbzhang commented Aug 23, 2021

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Aug 23, 2021
@openjdk
Copy link

openjdk bot commented Aug 23, 2021

@tbzhang
Your change (at version c791215) is now ready to be sponsored by a Committer.

@stefank
Copy link
Member

stefank commented Aug 23, 2021

/sponsor

@openjdk
Copy link

openjdk bot commented Aug 23, 2021

Going to push as commit 741f58c.
Since your change was applied there have been 86 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot closed this Aug 23, 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 Aug 23, 2021
@openjdk openjdk bot removed the sponsor Pull request is ready to be sponsored label Aug 23, 2021
@openjdk
Copy link

openjdk bot commented Aug 23, 2021

@stefank @tbzhang Pushed as commit 741f58c.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hotspot-gc hotspot-gc-dev@openjdk.org integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

4 participants