JDK-8221516 : fatal error: Thread SATB queue has an unexpected active state
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 13
  • Priority: P2
  • Status: Resolved
  • Resolution: Cannot Reproduce
  • Submitted: 2019-03-26
  • Updated: 2022-03-29
  • Resolved: 2019-05-05
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 13
13Resolved
Related Reports
Relates :  
JDK-8283898 - Shenandoah: Crash with thread SATB queue has an unexpected active state
Relates :  
JDK-8221102 - Allow GC threads to participate in threads claiming protocol
Relates :  
JDK-8220671 - Initialization race for non-JavaThread PtrQueues
Description
Test runtime/logging/RedefineClasses.java crashed with 
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (/scratch/opt/mach5/mesos/work_dir/slaves/2dd962d0-8988-479b-a804-57ab764ada59-S1217/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/ef2c44b1-f244-407c-8098-2fe454856ec1/runs/8cc15950-d80d-4a5c-baf8-0e80107b82f3/workspace/open/src/hotspot/share/gc/shared/satbMarkQueue.cpp:160), pid=5957, tid=5991
#  fatal error: Thread SATB queue has an unexpected active state
#
# JRE version: Java(TM) SE Runtime Environment (13.0+13) (fastdebug build 13-ea+13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 13-ea+13, mixed mode, sharing, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# V  [libjvm.so+0x14be7a5]  SATBMarkQueueSet::verify_active_states(bool)::VerifyThreadStatesClosure::do_thread(Thread*)+0xd5
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
Comments
Doesn't seem to be reproducible after fixing JDK-8220671 and JDK-8221102, either of which could give rise such a failure.
13-11-2019
No crashes after 7200 retries with latest jdk/jdk. Very likely fixed with some of the above mentioned changes.
01-05-2019
The thread found to be in the wrong state is a NonJavaThread (non_java_threads_do is on the stack). Might also be JDK-8220671.
29-03-2019
May be caused by the same issue JDK-8221102 fixes, so linking.
27-03-2019