-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
8-shenandoah, 11-shenandoah, 14, 15
As the more complicated followup for JDK-8246097, we might even consider walking the CLDG without _claim_strong and avoid clearing the marks before the walk. The only problem is that we need to make sure every path does _claim_none. And there are, unfortunately, paths through shared OopIterateClosures that default to _claim_strong, for example MetadataVisitingOopIterateClosure.
POC:
http://cr.openjdk.java.net/~shade/8246101/8246101-poc.patch
POC:
http://cr.openjdk.java.net/~shade/8246101/8246101-poc.patch
- duplicates
-
JDK-8253481 Shenandoah: ShenandoahConcurrentRootScanner::oops_do() should always use _claim_strong for CLDClosure
-
- Closed
-
- relates to
-
JDK-8246097 Shenandoah: limit parallelism in CLDG root handling
-
- Resolved
-