-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b11
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8277317 | 11.0.15-oracle | Fairoz Matte | P4 | Resolved | Fixed | b01 |
JDK-8278483 | 11.0.15 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
When concurrently unloading classes, it is possible for MDOs to have stale metadata entries in them until the GC comes around to clean it up. That is fine, but there is one place where care needs to be taken; when the compiler interface fetches ReceiverTypeData. This is done by memcpy:ing the ReceiverTypeData to a new memory buffer, and walking the metadata, patching it with corresponding ci metadata classes in the new buffer. The metadata could be stale by now. In such scenarios, the rows should be lazily cleaned.
- backported by
-
JDK-8277317 Prepare ciReceiverTypeData::translate_receiver_data_from for concurrent class unloading
-
- Resolved
-
-
JDK-8278483 Prepare ciReceiverTypeData::translate_receiver_data_from for concurrent class unloading
-
- Resolved
-