-
Enhancement
-
Resolution: Fixed
-
P4
-
12
-
b18
The VM thread code a few issue:
- It can create an extra safepoint directly after a safepoint.
- It's not safe for a non-JavaThread to add safepoint to queue while GC do oops do.
- The exposure of the vm operation is dangerous if it's a handshake.
- The code is a hornets nest with the repetition of checks and branches
- It can create an extra safepoint directly after a safepoint.
- It's not safe for a non-JavaThread to add safepoint to queue while GC do oops do.
- The exposure of the vm operation is dangerous if it's a handshake.
- The code is a hornets nest with the repetition of checks and branches
- relates to
-
JDK-8253833 mutexLocker assert_locked_or_safepoint should not access VMThread state from non-VM-thread
-
- Resolved
-
-
-
- Closed
-
-
-
- Resolved
-
-
-
- Resolved
-
(1 links to)