JDK-8255400 : Shenandoah: C2 failures after JDK-8255000
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 8-shenandoah,11,15,16
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2020-10-26
  • Updated: 2021-01-13
  • Resolved: 2020-11-02
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 16
16 b23Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
Summary is provisionary, adjust when finding more details.

Many tests exhibit the following assert with Shenandoah:

#  Internal Error (/home/rkennke/src/openjdk/jdk/src/hotspot/share/gc/shenandoah/c2/shenandoahSupport.cpp:1909), pid=358095, tid=358108
#  Error: assert(controls.member(u->in(0))) failed

See also attached hs_err and replay files.

Reproduced by (for example):
make run-test TEST=vmTestbase/nsk/jdi/ThreadReference/forceEarlyReturn/forceEarlyReturn006/TestDescription.java TEST_VM_OPTS="-XX:+UseShenandoahGC"

Bisecting shows that this regression is caused by JDK-8255000.
Comments
Changeset: a3aad119 Author: Roland Westrelin <roland@openjdk.org> Date: 2020-11-02 15:48:14 +0000 URL: https://github.com/openjdk/jdk/commit/a3aad119
02-11-2020

I added other affects-versions. Even though it is triggered by a jdk16 change, it may be useful (and should not hurt) to backport it to keep code in sync.
02-11-2020