| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8083190 | emb-9 | Filipp Zhinkin | P3 | Resolved | Fixed | team |
| JDK-8086507 | 8u65 | Boris Molodenkov | P3 | Resolved | Fixed | b01 |
| JDK-8065977 | 8u60 | Boris Molodenkov | P3 | Resolved | Fixed | b14 |
| JDK-8137565 | emb-8u65 | Unassigned | P3 | Resolved | Fixed | b01 |
| JDK-8079954 | emb-8u60 | Boris Molodenkov | P3 | Resolved | Fixed | team |
In order to inflate monitor associated with newly created object these tests use method rtm.AbortProvoker::inflateMonitor.
After that monitor remains released until actual testing begins. If safepoint synchronization happens when monitor unused, then that monitor will be deflated. As a result RTM-based lock elision won't be used and tests will fail.
Issue could be reproduced w/ +DeoptimizeALot.
- backported by
-
JDK-8065977 compiler/rtm/ tests fail due to monitor deflation at safepoint synchronization
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- blocks
-
JDK-8049355 compiler/rtm/locking/TestRTMLockingThreshold test may fail if transaction was aborted by interrupt
-
- Resolved
-
- is blocked by
-
JDK-8068272 Extend WhiteBox API with methods that check monitor state and force safepoint
-
- Resolved
-