JVM Crashing during GC - Problematic frame: V [libjvm.so+0x7ffedc] G1ParCopyClosure<(G1Barrier)0, (G1Mark)1>::do_oop(unsigned int*)+0x2ec
medhost-nwatson opened this issue · 2 comments
Thank you for taking the time to help improve OpenJDK and Corretto 11.
If your request concerns a security vulnerability then please report it by email to aws-security@amazon.com instead of here.
(You can find more information regarding security issues at https://aws.amazon.com/security/vulnerability-reporting/.)
Otherwise, if your issue concerns OpenJDK 11 and is not specific to Corretto 11 we ask that you raise it to the OpenJDK community. Depending on your contributor status for OpenJDK, please use the JDK bug system or
the appropriate mailing list for the given problem area or update project.
If your issue is specific to Corretto 11, then you are in the right place. Please proceed with the following.
Describe the bug
We have started seeing JRE crashes during G1GC (at least we think we are interpreting that correctly) in production.
To Reproduce
We have not yet been able to identify a specific action to trigger the error. Are hoping for some feedback that can help us identify that.
Expected behavior
JRE to continue running through GC.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform information
RHEL 8.8
Version Corretto-11.0.11.9.1
Additional context
Yes we know this is an older build of corretto but due to constraints of the production environment, it is not easy to move to higher release and test.
For VM crashes, please attach the error report file. By default the file name is hs_err_pidpid.log, where pid is the process ID of the process.
Hi, thanks for reaching out.
I'm still looking through your crash logs, but some initial observations - your release is 11.0.11, which is over 2 years and 10 releases old at this point, meaning you're missing hundreds of patches.
My first suggestion would be to try with the latest corretto 11.0.21 release and see if that resolves the issue.
@medhost-nwatson Any chance you tried the latest JDK?