-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8276125: RunThese24H.java SIGSEGV in JfrThreadGroup::thread_group_id #6702
Conversation
👋 Welcome back mgronlun! A progress list of the required criteria for merging this PR into |
@mgronlun 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 26 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 |
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 fine. Probably affects all releases, right? Even before Thread-SMR, the thread oop is not really guaranteed to be here?
"Looks fine. Probably affects all releases, right? Even before Thread-SMR, the thread oop is not really guaranteed to be here?" I don't really remember. This is old code, but the sightings started to appear in the last couple of months. Perhaps it is a combo of SMR thread lists AND the Access API coming together? The earlier API in javaClasses.cpp handling null perhaps? |
/integrate |
Going to push as commit a885aab.
Your commit was automatically rebased without conflicts. |
/backport jdk17u-dev |
@mmyxym the backport was successfully created on the branch backport-mmyxym-a885aab6 in my personal fork of openjdk/jdk17u-dev. To create a pull request with this backport targeting openjdk/jdk17u-dev:master, 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/jdk17u-dev:
|
Hi, where is the |
Unfortunately, this test is in an internal, non-public, repository. |
Greetings,
please help review this changeset.
Details are listed in the JIRA issue.
Testing: jdk_jfr
Thanks
Markus
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6702/head:pull/6702
$ git checkout pull/6702
Update a local copy of the PR:
$ git checkout pull/6702
$ git pull https://git.openjdk.java.net/jdk pull/6702/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6702
View PR using the GUI difftool:
$ git pr show -t 6702
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6702.diff