-
Enhancement
-
Resolution: Fixed
-
P4
-
14
-
b12
The ServiceThread has a list of all the OopStorage objects it needs to visit to perform cleanup actions (calling delete_empty_block) on them. Unfortunately, it's very easy to forget (or not know) the ServiceThread needs to be updated when a new OopStorage object is added. Some mechanism is needed to address this. Such a mechanism needs to be careful not to interfere with "anonymous" storage objects created as part of gtests.
- relates to
-
JDK-8230118 32-bit build failures after JDK-8227054
-
- Resolved
-
-
JDK-8227653 Add VM Global OopStorage
-
- Resolved
-
-
JDK-8229998 Build failure after JDK-8227054
-
- Resolved
-
-
JDK-8226366 Excessive ServiceThread wakeups for OopStorage cleanup
-
- Resolved
-
-
JDK-8227053 ServiceThread cleanup of OopStorage is missing some
-
- Resolved
-