Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8247878

Move Management strong oops to OopStorage

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Fixed
    • P3
    • 16
    • 16
    • hotspot
    • None
    • svc
    • b07

    Description

      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().

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JDK-8251302 Create dedicated OopStorages for Management and Jvmti

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-8273902 Memory leak in OopStorage due to bug in OopHandle::release()

          • P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Enhancement - null JDK-8247808 Move JVMTI strong oops to OopStorage

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Enhancement - null JDK-8247920 Unify handling of all OopStorage instances in root processing

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              coleenp Coleen Phillimore
              coleenp Coleen Phillimore
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: