-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8364159: Shenandoah assertions after JDK-8361712 #26513
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
8364159: Shenandoah assertions after JDK-8361712 #26513
Conversation
👋 Welcome back stuefe! A progress list of the required criteria for merging this PR into |
@tstuefe 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 34 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 |
MacOS error unrelated |
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.
Thanks for fixing this, I checked for similar code locations but could not find any (hope I did not overlook something).
The fix fixes our various asserts we saw across jtreg HS tests when enabling CompressedObjectHeaders by default,
Thanks @MBaesken ! My own tests are also clean now. Any shenandoah devs willing to give me a quick review? |
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.
Yes, please integrate. Seeing failure in current testing as well.
/integrate |
Going to push as commit 317dacc.
Your commit was automatically rebased without conflicts. |
In
ShenandoahAsserts::extract_klass_safely
, we attempt to carefully extract the Klass for an object and trip over our own feet doing this. We load the Markword twice: once to read "is_marked" and get the forwardee, once to extract the narrowKlass.If between the first and the second load we did evacuate the object concurrently, this happens:
T1 : fwd = SheandoahForwarding::get_forwardee_raw_unchecked(obj) => obj unmarked => (fwd == obj)
T2 : (installs forwarding pointer in obj)
T1: read markword from fwd again, (fwd == obj) => reads markword from forwarded obj, interprets the zeros in the upper part of the forwardee address as narrowKlass == 0, asserts
The solution is - as ShenandoahForwarding::klass() already does - to load the MW from original obj only once. Patch does that.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26513/head:pull/26513
$ git checkout pull/26513
Update a local copy of the PR:
$ git checkout pull/26513
$ git pull https://git.openjdk.org/jdk.git pull/26513/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26513
View PR using the GUI difftool:
$ git pr show -t 26513
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26513.diff
Using Webrev
Link to Webrev Comment