-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8297285: Shenandoah pacing causes assertion failure during VM initialization #11360
Conversation
initialization Signed-off-by: Ashutosh Mehra <asmehra@redhat.com>
👋 Welcome back ashu-mehra! A progress list of the required criteria for merging this PR into |
@ashu-mehra The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
fix compile failure Signed-off-by: Ashutosh Mehra <asmehra@redhat.com>
zero build was failing with following compile error:
Pushed a commit to include the necessary header file. |
Can I please get reviews for this PR. |
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 good to me! Thank you, Ashu!
@ashu-mehra 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 240 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@rkennke, @phohensee) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
@rkennke thanks for suggesting and reviewing the fix. |
/integrate |
@ashu-mehra |
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'm not familiar with this code, so please bear with me. :) The comment on line 246 says "Thread which is not an active Java thread should also not block.", but the check at line 251 will return (i.e., looks like not block) if the current thread is an active Java thread. Should the check be !current->is_active_Java_thread() instead?
@phohensee you are right. It should be |
Signed-off-by: Ashutosh Mehra <asmehra@redhat.com>
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 good now.
/sponsor |
@phohensee The PR has been updated since the change author (@ashu-mehra) issued the |
/integrate |
@ashu-mehra |
/sponsor |
Going to push as commit 415cfd2.
Your commit was automatically rebased without conflicts. |
@phohensee @ashu-mehra Pushed as commit 415cfd2. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review the fix for the assertion failure seen during VM init due to pacing in shenandoah gc.
The fix is to avoid pacing during VM initialization as the main thread is not yet an active java thread.
Signed-off-by: Ashutosh Mehra asmehra@redhat.com
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11360/head:pull/11360
$ git checkout pull/11360
Update a local copy of the PR:
$ git checkout pull/11360
$ git pull https://git.openjdk.org/jdk pull/11360/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 11360
View PR using the GUI difftool:
$ git pr show -t 11360
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11360.diff