JDK-8283898 : Shenandoah: Crash with thread SATB queue has an unexpected active state
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 18
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • CPU: aarch64
  • Submitted: 2022-03-29
  • Updated: 2023-09-12
  • Resolved: 2023-09-12
Related Reports
Duplicate :  
Relates :  
Relates :  
Relates :  
Description
The VM has crashed on MacOS aarch64 (M1) while executing the following tests:
gc/shenandoah/TestLotsOfCycles.java#iu-aggressive
gc/shenandoah/TestJcmdHeapDump.java#iu-aggressive

A similar crash was reported with G1 at an earlier time: JDK-8221516

#  Internal Error (/darwinaarch64/jdk18u/src/hotspot/share/gc/shared/satbMarkQueue.cpp:169), pid=34167, tid=15107
#  fatal error: Thread SATB queue has an unexpected active state

V  [libjvm.dylib+0x59acd4]  report_fatal(VMErrorType, char const*, int, char const*, ...)+0x124
V  [libjvm.dylib+0xe90cbc]  SATBMarkQueueSet::verify_active_states(bool)::VerifyThreadStatesClosure::do_thread(Thread*)+0xd8
V  [libjvm.dylib+0x10a71e0]  Threads::threads_do(ThreadClosure*)+0x54
V  [libjvm.dylib+0xe8ffd4]  SATBMarkQueueSet::verify_active_states(bool)+0xec
V  [libjvm.dylib+0xe90050]  SATBMarkQueueSet::set_active_all_threads(bool, bool)+0x64
V  [libjvm.dylib+0xedf5e0]  ShenandoahConcurrentMark::finish_mark()+0x190
V  [libjvm.dylib+0xee2fc4]  ShenandoahDegenGC::op_degenerated()+0x1d8
V  [libjvm.dylib+0xee2d34]  ShenandoahDegenGC::entry_degenerated()+0x148
V  [libjvm.dylib+0xf7fc7c]  VM_ShenandoahDegeneratedGC::doit()+0x30
V  [libjvm.dylib+0x114fec0]  VM_Operation::evaluate()+0x104
V  [libjvm.dylib+0x116bc88]  VMThread::evaluate_operation(VM_Operation*)+0x12c
V  [libjvm.dylib+0x116c848]  VMThread::inner_execute(VM_Operation*)+0x33c
V  [libjvm.dylib+0x116b960]  VMThread::loop()+0xb4
V  [libjvm.dylib+0x116b748]  VMThread::run()+0xc0

Comments
Closing as duplicate of JDK-8288139. Feel free to reopen if this issue persists.
12-09-2023

Martin, if you have not seen these issues recently, I'll close the bug as duplicate of JDK-8288139.
28-06-2023

Both JDK-8288139 and JDK-8286830 can result this failure and JDK-8286830 exists since JDK11. Have you seen the failure lately? after JDK-8288139 and JDK-8286830? Thanks.
18-07-2022