-
Notifications
You must be signed in to change notification settings - Fork 121
8327501: Common ForkJoinPool prevents class unloading in some cases #338
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
8327501: Common ForkJoinPool prevents class unloading in some cases #338
Conversation
👋 Welcome back shade! 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. |
|
Lets wait on getting this one backported until the compatibility impact wrt. setting the context class loader of a thread in the common pool is addressed. |
Yup. With this PR, I just confirmed all tests that I throw at this change pass in jdk21u-dev. |
@shipilev 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 no new commits pushed to the ➡️ To integrate this PR with the above commit message to the |
f17aeca
to
6718471
Compare
/issue add JDK-8328366 |
@shipilev |
Both backports are clean. /clean |
@shipilev This backport pull request is now marked as clean |
0c1d5d9
to
febeb48
Compare
/approval 8327501 request Fixes the class unloading regression since JDK 19. Applies cleanly. Tests pass, but there is a regression, which is fixed by JDK-8328366. Risk is medium: affects common paths, has bugtail with easily detectable failures. /approval 8328366 request Fixes the regression introduced by JDK-8327501. Applies cleanly. Tests pass. |
Checking, @jerboaa, are you good with this going into jdk21u-dev? |
@shipilev Yes, though, a bit uneasy. It fixes the unloading issue. We'll have a close look once EA builds are available. Worst case we'll have to back it out during stabilization closer to the 21.0.5 release. |
All right, I am waiting a bit more to see if JDK 23 and 22.0.2 testing finds any issues with it. I plan to integrate this later in July if no issues are found. |
@shipilev This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
Not now, bot, everything goes according to plan. |
febeb48
to
a5c81e3
Compare
@shipilev Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
Re-based, re-tested, ready to integrate. Checking with @jerboaa -- go or no-go? |
Aye. /integrate |
Going to push as commit eb103b0.
Your commit was automatically rebased without conflicts. |
The change is stabilizing in mainline, but it looks simple, so we start testing it for JDK 21 pickup here.
Additional testing:
all
all
Progress
Issues
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/338/head:pull/338
$ git checkout pull/338
Update a local copy of the PR:
$ git checkout pull/338
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/338/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 338
View PR using the GUI difftool:
$ git pr show -t 338
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/338.diff
Webrev
Link to Webrev Comment