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

Make JVMTI TagMap table concurrent

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P3 P3
    • 16
    • 16
    • hotspot
    • b26

      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.

        1.
        		 Release Note: Make JVMTI Table Concurrent Sub-task Closed Coleen Phillimore  

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

              Created:
              Updated:
              Resolved: