JVM crash with EXCEPTION_ACCESS_VIOLATION

[CodyRay]

Describe the bug

On Windows servers we see intermittent crashes (less than 1% of runs, but happens about once a week)

To Reproduce

We haven't been able to reliably reproduce given the intermittent occurrences.

Expected behavior

JVM not to crash or provide a more specific cause.

Screenshots

N/A

Platform information

OS: Windows Server 2012 R2
Version: Corretto-17.0.3.6.1

Additional context

Some info about our setup that could be relevant... The crashes happen on our CI servers when running unit tests, but it has been a different tests in different modules for each failure. Failures have been in projects with a mix of Java and Kotlin or in pure a pure Kotlin project - we have few pure Java projects. Tests are ran using Gradle.

Attached logs for most recent three instances; seems our CI isn't configured to *.mdmp files i'll configure it to save any future ones.

hs_err_pid2300.log
hs_err_pid1640.log
hs_err_pid9108.log

[navyxliu]

okay. all 3 instances crashed in ""C2 CompilerThread1" . I will take closer look at assembly level.
Could you provide us a reproducible?

[CodyRay]

@navyxliu unfortunately with it being so intermittent, we don't have a reproduction - is there anything from the crash dump that might be able to inform how we could reproduce it?

[navyxliu]

I don't need coredump so far. let me inspect your stacktraces and see if it's a known issue.

[CodyRay]

@navyxliu wanted to let you know that we were able to capture a coredump with a new crash, so if that does become helpful I can provide that. Thanks!

[Zarp3]

@haroldhues hi friend I have the same error if you could help me I would appreciate it :)

[CodyRay]

@Zarp3 No luck here, we've tried upgrading to the latest corretto point fix and that seems to have reduced the frequency of the issue, but too early to tell

[eckama11]

Has this been solved yet? We are reproducing this also in our machines.

[CodyRay]

We're no longer experiencing this issue, we don't know what the fix ended up being but we are now on corretto 21