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

Make JVMTI TagMap table concurrent

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 16
    • Fix Version/s: 16
    • Component/s: hotspot
    • Subcomponent:
    • Resolved In Build:
      b26

      Description

      And use WeakHandles to point to the elements so that hashing doesn't have to be redone for GC.

      If we use OopStorage via WeakHandles, the GC can walk the oops concurrently. The oops were stored directly because there were unexpected NULL entries when they were jweak. I don't see why this would be a problem, except that the hashcode would be broken in this case. Making them use oop->identity_hash() would fix this. Unfortunately, identity_hash is the only hashcode that makes sense for any sort of oop that can be stored in the table.

      This anomalous table and its handling by GC is a problem area.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: