-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8343890: SEGV crash in RunTimeClassInfo::klass #22550
Conversation
👋 Welcome back matsaave! A progress list of the required criteria for merging this PR into |
@matias9927 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:
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 80 new commits pushed to the
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 |
@matias9927 The following label will be automatically applied to this pull request:
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
Thanks for the reviews @calvinccheung and @iklam! |
Going to push as commit bf0debc.
Your commit was automatically rebased without conflicts. |
@matias9927 Pushed as commit bf0debc. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
/backport jdk jdk24 |
@matias9927 the backport was successfully created on the branch backport-matias9927-bf0debc0-jdk24 in my personal fork of openjdk/jdk. To create a pull request with this backport targeting openjdk/jdk:jdk24, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk:
|
Some tests fail very intermittently due to RuntimeInfo::klass(), see the bug page for more details. This patch modifies the method to avoid the reported crash. Verified with tier 1-5 tests.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22550/head:pull/22550
$ git checkout pull/22550
Update a local copy of the PR:
$ git checkout pull/22550
$ git pull https://git.openjdk.org/jdk.git pull/22550/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 22550
View PR using the GUI difftool:
$ git pr show -t 22550
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22550.diff
Using Webrev
Link to Webrev Comment