-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8344773: SM cleanup in ForkJoinPool #22324
Conversation
👋 Welcome back dl! A progress list of the required criteria for merging this PR into |
@DougLea 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 41 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 |
Webrevs
|
@@ -84,7 +80,7 @@ public class ForkJoinWorkerThread extends Thread { | |||
super.setDaemon(true); | |||
if (handler != null) | |||
super.setUncaughtExceptionHandler(handler); | |||
if (useSystemClassLoader) | |||
if (useSystemClassLoader & !clearThreadLocals) // else done by Thread ctor |
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.
It might be clearer to use a conditional-and here although it doesn't make any difference here.
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.
I agree that "&&" would be clearer. Will do.
/** | ||
* Peforms any associated cleanup on resetThreadLocals | ||
*/ | ||
void onThreadLocalReset() { |
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.
@DougLea I'm wondering if it might be clearer if it was something like afterThreadLocalReset
or postThreadLocalReset
or something indicating that TLs have already expired by the point this is invoked.
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.
How about just being clearer about this in javadoc: Changed to:
/**
* Performs any further cleanup after ThreadLocals are cleared in
* method resetThreadLocals
*/
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.
I think this looks good.
/integrate |
Going to push as commit 3e509c8.
Your commit was automatically rebased without conflicts. |
Complete the SM cleanup in java.util.concurrent that was deferred during other FJP updates
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22324/head:pull/22324
$ git checkout pull/22324
Update a local copy of the PR:
$ git checkout pull/22324
$ git pull https://git.openjdk.org/jdk.git pull/22324/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 22324
View PR using the GUI difftool:
$ git pr show -t 22324
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22324.diff
Using Webrev
Link to Webrev Comment