-
Notifications
You must be signed in to change notification settings - Fork 208
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 #2179
Conversation
👋 Welcome back lmao! A progress list of the required criteria for merging this PR into |
This backport pull request has now been updated with issue from the original commit. |
|
/approval request Clean backport for fixing JFR crash. The root cause is creating threads in JNI function can overlap with the JFR safepoint op and accessing a NULL threadobj. The original commit fixed the potential NULL access. The risk is very low that it's a clean backport and the null pointer check is rather simple. |
@mmyxym 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 5 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the As you do not have Committer status in this project an existing Committer must agree to sponsor your change. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
Could committers please help sponsor, thanks! |
Yes, this makes sense, thanks. /sponsor |
Going to push as commit 2500dbe.
Your commit was automatically rebased without conflicts. |
Aleksey, thanks! |
Clean backport for fixing JFR crash. The root cause is creating threads in JNI function can overlap with the JFR safepoint op and accessing a NULL threadobj. The original commit fixed the potential NULL access.
Additional testing:
Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/2179/head:pull/2179
$ git checkout pull/2179
Update a local copy of the PR:
$ git checkout pull/2179
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/2179/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 2179
View PR using the GUI difftool:
$ git pr show -t 2179
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/2179.diff
Webrev
Link to Webrev Comment