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

Shenandoah: ShenandoahConcurrentRootScanner::oops_do() should always use _claim_strong for CLDClosure

XMLWordPrintable

    • gc

      _claim_none should only be used for single thread scanning, regardless concurrent or not.

       ShenandoahConcurrentRootScanner declares ShenandoahClassLoaderDataRoots multi-thread capable, so should always use _claim_strong for scanning CLDG.

      This is not a correctness bug. _claim_none results CLDG to be scanned by every worker.

            zgu Zhengyu Gu
            zgu Zhengyu Gu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: