| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8082767 | emb-9 | Per Liden | P4 | Resolved | Fixed | team |
We currently have two use patterns of the SuspendibleThreadSet. In most cases a SuspendibleThreadSetJoiner is placed on the stack. This is nice because ensures that you don't forget to leave the set. The other cases use direct calls to SuspendibleThreadSet::join() and SuspendibleThreadSet::leave(), and this is typically used when there's a need to temporary leave the set in the middle of some block of logic. I propose that we add a SuspendibleThreadSetLeaver to accompany the SuspendibleThreadSetJoiner and make it the only way to join/leave the set.
- backported by
-
JDK-8082767 Add SuspendibleThreadSetLeaver and make SuspendibleThreadSet::joint()/leave() private
-
- Resolved
-
- duplicates
-
JDK-7098506 G1: Introduce safer STS join/leave (and vice versa) critical sections
-
- Closed
-