-
Notifications
You must be signed in to change notification settings - Fork 710
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JDK17 Assertion Failed with memoryCorruptionDetected #15639
Comments
@tajila fyi |
Failing thread
|
@ChengJin01 Can you please take a look at this |
which means the error message was successfully created & printed to the message buffer but the crash occurred when releasing the stackmape frame memory afterwards at
against the code in
against the code in
It seems the problem was triggered somewhere in
which means
which means there is no element of 'locals' and 'stack' in the current stackmap frame in which case the code above didn't handle at this point. |
Looking at the Verification error message generated by HotSpot as follows:
which shows it captured the error with So there might be two issues with our code:
|
FYI: @DanHeidinga |
I will be on vacation next week and get back to keep working on this issue. |
With my fix at ChengJin01@b557b59, the assertion was resolved and ended up with the expected error message as follows:
which indicates the class (version <= 50) was verified with the older verifier (fallback). So it matches RI's output in the case of non-fallback by specifying
|
Hi @lochnagarr, please specify |
The change is to resolve the crash issue specific to a stackmap frame without any element in 'locals' and 'stack' when allocating the memory of stackmap frame in the error message framework during the runtime verification. Fixes: eclipse-openj9#15639 Signed-off-by: Cheng Jin <jincheng@ca.ibm.com>
Java -version output
openjdk version "17.0.3" 2022-04-19
IBM Semeru Runtime Open Edition 17.0.3.0 (build 17.0.3+7)
Eclipse OpenJ9 VM 17.0.3.0 (build openj9-0.32.0, JRE 17 Linux amd64-64-Bit Compressed References 20220422_184 (JIT enabled, AOT enabled)
OpenJ9 - 9a84ec3
OMR - ab24b6666
JCL - dc07fd49b92 based on jdk-17.0.3+7)
Summary of problem
When running a buggy classfile generated by a fuzzer, JVM crashes and we get the following message:
We have collected the related classfiles and dependencies in bug_memory.zip:
bug_memory.zip
The buggy classfile is in
bug_memory/bug_file
To reproduce this issue, enter
bug_memory
and run the following command:To avoid this issue, run
Adding
-noverify
will also avoid this issue, but may lead toSegmentation error vmState=0x00000000
We also tested this in HotSpot, and the buggy classfile leads to a VerifyError.
Diagnostic files
javacore.20220728.135359.622426.0002.txt
Snap.20220728.135359.622426.0003.zip
The text was updated successfully, but these errors were encountered: