JDK-8293832 : Kitchensink24HStress.java failed with EXCEPTION_ACCESS_VIOLATION in a C-frame
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 20
  • Priority: P2
  • Status: Open
  • Resolution: Unresolved
  • OS: windows
  • CPU: x86_64
  • Submitted: 2022-09-15
  • Updated: 2022-10-01
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 20
20Unresolved
Related Reports
Relates :  
JDK-8258825 - strange crashes with applications/jcstress on AMD EPYC
Relates :  
JDK-8293648 - Kitchensink.java failed with SIGSEGV in compiled frame with ZGC
Description
The following test failed in the JDK20 CI:

applications/kitchensink/Kitchensink24HStress.java

Here's the crashing thread's stack:

---------------  T H R E A D  ---------------

Current thread (0x0000020d52996260):  JavaThread "SpecJvm2008BatchStressModule" [_thread_in_Java, id=5004, stack(0x0000002acca00000,0x0000002accb00000)]

Stack: [0x0000002acca00000,0x0000002accb00000],  sp=0x0000002accaf9c50,  free space=999k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  0x0000020b3d38eced


siginfo: EXCEPTION_ACCESS_VIOLATION (0xc0000005), reading address 0xffffffffffffffff
Comments
Happened with ZGC, so possibly related to JDK-8293648.
01-10-2022
Linking to JDK-8258825 in case it is related to the "only happens on EPYC" failures.
16-09-2022
RDX, R8, and R9 should be the incoming arguments. All three look bad. Windows might have reported 0xffffffffffffffff instead of the real address because 0xb80000017800000c is not a valid "canonical" address. A canonical address has bit 47 sign-extended to bits 48-63.
16-09-2022
ILW = Crash in C code, single occurrence but might be related to recently reported crashes, no workaround = HLH = P2
15-09-2022
This failure is very similar to other recent failures that the HotSpot compiler team is looking at so I'm starting this bug in hotspot/compiler.
15-09-2022