JDK-8259504 : runtime/ReservedStack/ReservedStackTest.java crashes with assert(_stack_guard_state == stack_guard_reserved_disabled) failed: inconsistent state
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 16
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2021-01-08
  • Updated: 2021-05-13
  • Resolved: 2021-05-13
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 17
17Resolved
Related Reports
Duplicate :  
Relates :  
Description
Test
runtime/ReservedStack/ReservedStackTest.java
crashes with 
# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc:  SuppressErrorAt=/stackOverflow.cpp:147
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (/opt/mach5/mesos/work_dir/slaves/983c483a-6907-44e0-ad29-98c7183575e2-S14503/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/57fe762f-16a3-482f-aca4-85f8f51a0206/runs/465b3bb9-61c5-4302-ab3a-6e9b91be4cae/workspace/open/src/hotspot/share/runtime/stackOverflow.cpp:147), pid=22666, tid=22835
#  assert(_stack_guard_state == stack_guard_reserved_disabled) failed: inconsistent state
#
# JRE version: Java(TM) SE Runtime Environment (16.0+28) (fastdebug build 16-ea+28-2065)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 16-ea+28-2065, compiled mode, sharing, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# V  [libjvm.so+0x177aa06]  StackOverflow::enable_stack_reserved_zone(bool)+0x46
#
# Core dump will be written. Default location: Core dumps may be processed with "/opt/core.sh %p" (or dumping to /opt/mach5/mesos/work_dir/slaves/983c483a-6907-44e0-ad29-98c7183575e2-S82541/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/a13691d1-a6ad-4607-8387-8a7200fa2dbd/runs/283d64f8-8fee-447d-b311-981b062e264c/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_runtime/scratch/1/core.22666)
#
# An error report file with more information is saved as:
# /opt/mach5/mesos/work_dir/slaves/983c483a-6907-44e0-ad29-98c7183575e2-S82541/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/a13691d1-a6ad-4607-8387-8a7200fa2dbd/runs/283d64f8-8fee-447d-b311-981b062e264c/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_runtime/scratch/1/hs_err_pid22666.log
Compiled method (c2)   12197 5076       4       ReservedStackTest$ReentrantLockTest::lockAndCall (29 bytes)
 total in heap  [0x00007fe189528810,0x00007fe1895293d0] = 3008
 relocation     [0x00007fe189528988,0x00007fe189528a78] = 240
 main code      [0x00007fe189528a80,0x00007fe189528de0] = 864
 stub code      [0x00007fe189528de0,0x00007fe189528e50] = 112
 oops           [0x00007fe189528e50,0x00007fe189528e58] = 8
 metadata       [0x00007fe189528e58,0x00007fe189528e88] = 48
 scopes data    [0x00007fe189528e88,0x00007fe189529030] = 424
 scopes pcs     [0x00007fe189529030,0x00007fe189529310] = 736
 dependencies   [0x00007fe189529310,0x00007fe189529318] = 8
 handler table  [0x00007fe189529318,0x00007fe1895293a8] = 144
 nul chk table  [0x00007fe1895293a8,0x00007fe1895293d0] = 40
#
# If you would like to submit a bug report, please visit:
#   https://bugreport.java.com/bugreport/crash.jsp
Comments
I ran the fixed version of the test from JDK-8231031, 50x across all platforms using the test flags from tiers 1 through 8 (total of 1408 test runs) with zero failures or crashes. I'm going to close this bug as a dup of JDK-8231031.
13-05-2021

I'm re-testing to see if I can reproduce this, but I suspect I will have to close as not reproducible.
11-05-2021

[~lmesnik] thanks for the key flag info: -Xcomp -ea -esa -XX:CompileThreshold=100 -XX:+TieredCompilation Unfortunately I seem unable to reproduce this crash, or any other failure mode so far.
23-02-2021

[~lmesnik] do you know what the command-line was for this report? Were there any special flags being passed? Thanks.
23-02-2021

ILW = HLM = P3
12-01-2021

This may be the debug failure mode for what is observed in JDK-8231031, but I will see if I can reproduce.
11-01-2021

The test is problem listed because of JDK-8231031. However, this bug looks different.
08-01-2021