-
Bug
-
Resolution: Fixed
-
P3
-
19, 20
-
b15
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8293730 | 19.0.2 | Robert Mckenna | P3 | Resolved | Fixed | b01 |
JDK-8293688 | 19.0.1 | Robert Mckenna | P3 | Resolved | Fixed | b10 |
If a blocking operation such as Object.wait pins a virtual thread to its carrier thread, and if that operation doesn't activate a spare, then subsequent blocking operations that pin a virtual thread to this carrier thread do not attempt to activate a spare. In other words, if Blocker.begin returns 0 with the carrier thread's blocking flag set then Blocker.end will not reset the blocking flag.
- backported by
-
JDK-8293688 CarrierThread.blocking not reset when spare not activated
-
- Resolved
-
-
JDK-8293730 CarrierThread.blocking not reset when spare not activated
-
- Resolved
-
- links to
-
Commit openjdk/jdk19u/0c71773f
-
Commit openjdk/jdk/68da02c7
-
Review openjdk/jdk19u/22
-
Review openjdk/jdk/9841
(1 links to)