-
Bug
-
Resolution: Fixed
-
P4
-
11, 17, 20, 21, 22, 23
-
b08
See https://github.com/openjdk/jdk/pull/11996#issuecomment-1409331760 If any thread can potentially repack the extra data section then any code path which might receive data from the extra data section must guard against this by holding the lock. JVMCI in general isn't exposed to this problem since it doesn't create speculative trap data entries. It's probably likely to be exceeding rare since I guess this only occurs with ZGC.
- relates to
-
JDK-8215889 assert(!_unloading) failed: This oop is not available to unloading class loader data with ZGC
- Resolved
-
JDK-8231501 VM crash in MethodData::clean_extra_data(CleanExtraDataClosure*): fatal error: unexpected tag 99
- Resolved
-
JDK-8324129 C2: Remove some ttyLocker usages in preparation for JDK-8306767
- Resolved