-
Bug
-
Resolution: Fixed
-
P1
-
20
-
b03
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8298780 | 20 | Stefan Karlsson | P1 | Resolved | Fixed | b29 |
Before that change we made sure that only the GC performed load barriers on the cont oop in stackChunk, so that we could use the oop state as an indication of the age of the stackChunk. That information was then used in ZCollectedHeap::requires_barriers.
In Generational ZGC we changed the implementation of requires_barriers, so that the rest of the JVM didn't need to have special-handling of the cont oop. However, when upstreaming the changes in
To limit the fix for this bug, I propose that we restore the special-handling of the cont oop.
- backported by
-
JDK-8298780 ZGC: thaws stackChunk with stale oops
-
- Resolved
-
- duplicates
-
JDK-8298058 jdk/internal/vm/Continuation/Fuzz.java#default fails "assert(oopDesc::is_oop_or_null(val)) failed: bad oop found at 0xNNNN in_cont: 0 compressed: 0"
-
- Closed
-
- relates to
-
JDK-8298058 jdk/internal/vm/Continuation/Fuzz.java#default fails "assert(oopDesc::is_oop_or_null(val)) failed: bad oop found at 0xNNNN in_cont: 0 compressed: 0"
-
- Closed
-
- links to
-
Commit openjdk/jdk20/48f61273
-
Commit openjdk/jdk/ed8a2120
-
Review openjdk/jdk20/37
-
Review openjdk/jdk/11585