Set thread.started after running <init> #18310
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
jenkins test sanity alinux64 jdk21 |
|
jenkins test sanity alinux64 jdk21 |
Current we set `thread.started = true` for system threads before running the constructor. This causes a race condition where the thread object may be made visible while it is being constructed potentially causing NPEs. Signed-off-by: Tobi Ajila <[email protected]>
|
jenkins test sanity alinux64 jdk21 |
babsingh
approved these changes
Oct 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently we set
thread.started = truefor system threads before running the constructor. This causes a race condition where the thread object may be made visible while it is being constructed potentially causing NPEs.