JDK-8312534 : [linux x86] assert in g1ConcurrentMark.cpp: Overflow during reference processing
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 22
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • OS: linux
  • CPU: x86
  • Submitted: 2023-07-22
  • Updated: 2023-07-24
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 22
22Unresolved
Related Reports
Relates :  
Description
I've seen this several times over the last weeks, always on x86.

https://github.com/tstuefe/jdk/actions/runs/5629505655/attempts/1#user-content-tools_javac_lambda_bytecode_testlambdabytecodetargetrelease14

```
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (g1ConcurrentMark.cpp:1671), pid=23144, tid=23154
#  fatal error: Overflow during reference processing, can not continue. Current mark stack depth: 65472, MarkStackSize: 65536, MarkStackSizeMax: 4194304. Please increase MarkStackSize and/or MarkStackSizeMax and restart.
#
# JRE version: OpenJDK Runtime Environment (22.0) (build 22-internal-tstuefe-c3ce46f4f7cb41000afc6a4a7de7c990817c1ee1)
# Java VM: OpenJDK Server VM (22-internal-tstuefe-c3ce46f4f7cb41000afc6a4a7de7c990817c1ee1, mixed mode, tiered, g1 gc, linux-x86)
# Problematic frame:
# V  [libjvm.so+0x5c18eb]  G1ConcurrentMark::weak_refs_work()+0x31b
#
# CreateCoredumpOnCrash turned off, no core file dumped
#
# If you would like to submit a bug report, please visit:
#   https://bugreport.java.com/bugreport/crash.jsp
#
```

I *believe*, but I may be wrong, that I saw these errors first creep up short after JDK-8281455. It would be a bit weird though, since those changes should have no effect on 32-bit.
Comments
[~kbarrett] Not always the same test, though limited to just a few, and always tool tests. Tests I have seen crashing so far: tools/javac/lambda/bytecode/TestLambdaBytecodeTargetRelease14 tools/javac/varargs/warning/Warn5 https://github.com/tstuefe/jdk/actions/runs/5612767875/attempts/1#summary-15210606694 It is annoying since it hits every third or so GHA run. People get used to x86 failing, that's not good. Maybe we should problemlist those tests for x86.
24-07-2023

That mark stack overflow during reference processing crashes is a known issue - JDK-8280087.
24-07-2023

[~stuefe] Is it always the same test that fails? I looked at JDK-8281455, and I agree that if it's not at all obvious how it could be the culprit.
24-07-2023