[aarch64-port-dev ] [8u] 8231366: Shenandoah: Shenandoah String Dedup thread is not properly initialized

Zhengyu Gu zgu at redhat.com
Mon Sep 23 16:24:39 UTC 2019


This bug seems to exist since day one of 8u backport. The 
ConcurrentGCThread API is different in 8u and we leave 
ShenandoahDedupThread not properly initialized before it enters work loop.

In Shenandoah String Deduplication tests, the bug results assertion 
failure that shows Thread::current() == NULL.

The bug only manifests on Windows, is due to discrepancy of java_start() 
implementation on different OSs. e.g. it sets *thread* on Linux.

Bug: https://bugs.openjdk.java.net/browse/JDK-8231366
Webrev: http://cr.openjdk.java.net/~zgu/JDK-8231366/webrev.00/

Test:
   hotspot_gc_shenandoah on Windows and Linux.

Thanks,

-Zhengyu



More information about the aarch64-port-dev mailing list