-
Notifications
You must be signed in to change notification settings - Fork 729
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
HeapHogLoadTest_5m_0_FAILED Segmentation error vmState=0x00000000 #19456
Comments
@knn-k can you pls take the first look at the core. |
It is a SEGV caused by an instruction trying to load from an address pointed by
|
|
Many registers in the register dump have the addresses of a specific region. The memory dump looks like a table of addresses.
|
@knn-k DDR cmds to find the location of the crash in the interpreter:
|
I don't see the symptoms from #14713 (comment). But, this crash looks like the reverse of #14713 (comment).
|
If there is a J2I frame, then the jitStackFrameFlags have already been consumed. Is the invokebasic coming from the interpreted method that's running in the J2I frame? |
Yes, bytecode 13 in the J2I frame is an invokebasic. |
That contradicts your statement:
as we are running in an interpreted method that was invoked by the JIT. |
The JIT would not have set up the arguments for invokebasic. The |
I see. So, we are taking the For the interpreted method (
|
Given that the previous frame is a jitted method, yes. |
The crash happened on an amac: https://na.artifactory.swg-devops.com/artifactory/sys-rt-generic-local/hyc-runtimes-jenkins.swg-devops.com/Test_openjdk22_j9_extended.system_aarch64_mac_testList_0/10/system_test_output.tar.gz. I am unable to view the native stack in lldb. Can anyone see the line of code in lldb where the crash happened? |
OpenJ9 for AArch64 macOS does not support native stack backtrace: Issue #15925. |
JDK17 aarch64_mac(
50x grinder - passed |
DDR is reporting corrupt data while iterating the O-slots of the J2I frame. Since the arguments on the stack are being populated by the JIT, @nbhuiyan can you please check if the JIT is supplying the correct arguments for the J2I frame? |
https://openj9-jenkins.osuosl.org/job/Test_openjdk22_j9_extended.system_aarch64_mac_Nightly_testList_2/2
|
I ran two 30x Grinder jobs, and got one failure:
|
Why is there never a native stack trace? |
jdk24 testing https://openj9-jenkins.osuosl.org/job/Test_openjdknext_j9_extended.system_aarch64_mac_Nightly_testList_2/66 - mac11-aarch64-4a
|
This seems a dup of #19081 |
Closing as a dup of #19081 |
Issue Number: 19456 |
Failure link
From an internal build(
macaarch64rt8
):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
50x internal grinder - 2/50 failed at
macaarch64rt5
There was a similar failure:
The text was updated successfully, but these errors were encountered: