-
Enhancement
-
Resolution: Fixed
-
P4
-
12
-
b24
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8216248 | 13 | Zhengyu Gu | P4 | Resolved | Fixed | team |
During upstreaming ShenandoahTaskTermination and investigating inconsistent termination state reported by Thomas Schatzl, I believe we don't have to offer termination from every worker threads, since task termination should reach consistent state at then end, regardless it is normal or aborted termination (see JDK-8215047 for details).
That says, Shenandoah can dramatically simplify task termination logic, and eliminates ShenandoahCancelledTerminatorTerminator.
This work does not depend on fixing ofJDK-8215047, because it does not reuse terminator.
That says, Shenandoah can dramatically simplify task termination logic, and eliminates ShenandoahCancelledTerminatorTerminator.
This work does not depend on fixing of
- backported by
-
JDK-8216248 Simplify Shenandoah task termination in aborted paths
-
- Resolved
-
- blocks
-
JDK-8215047 Task terminators do not complete termination in consistent state
-
- Resolved
-