corretto/corretto-8

crash during pyspak runing

kutib opened this issue · 1 comments

kutib commented

Thank you for taking the time to help improve OpenJDK and Corretto.

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 8 and is not specific to Corretto 8 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 jdk8u-dev.

If your issue is specific to Corretto 8,
then you are in the right place.
Please proceed with the following.

Describe the bug

A clear and concise description of what the bug is.

To Reproduce

Steps and (source) code to reproduce the behavior.

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

If applicable, add screenshots to help explain your problem.

Platform information

OS: [e.g. Amazon Linux 2]
Version [e.g. "build 1.8.0_192-amazon-corretto-preview-b12" (output from "java -version")]

Additional context

Add any other context about the problem here.

[thread 140603593746176 also had an error]#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fe197a63365, pid=8, tid=0x00007fe0d3022700
#
# JRE version: OpenJDK Runtime Environment (8.0_392-b08) (build 1.8.0_392-b08)
# Java VM: OpenJDK 64-Bit Server VM (25.392-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.so+0x7e8365]

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 reporting this. It looks like a few of the details requested in the bug template are missing. Could you include a brief description of how to reproduce the error, and, if possible, the hs_err file from the crash?