Move Management strong oops to OopStorage

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P3
    • 16
    • Affects Version/s: 16
    • Component/s: hotspot
    • None
    • svc
    • b07

      ThreadService and MemoryService implementations collect information at a safepoint and after the safepoint create objects to pass back to Java code. The oops they collect are saved directly in the data structures necessitating an oops_do() call on them. If the oops are moved to OopStorage, they can be iterated more efficiently by GC. Also all the GCs won't require a case to call Management::oops_do().

            Assignee:
            Coleen Phillimore
            Reporter:
            Coleen Phillimore
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: