-
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
OpenJDK java/lang/Thread/virtual/stress/GetStackTraceALotWhenPinned Invalid JIT return address ASSERTION FAILED swalk.c:1629: ((0 )) #18910
Comments
Perhaps related to #18908 |
Saw a failure with a different symptom in an internal grinder run https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder/37939:
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk22_j9_sanity.openjdk_x86-64_mac_Nightly_testList_1/15/
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk22_j9_sanity.openjdk_x86-64_mac_Nightly_testList_0/28
|
Any new news on this one? |
I haven't been able to make further progress on this one. |
@hzongaro we won't hold the release for this, pls move it out of the Java 22 milestone. |
JDK22 x86-64_mac(
50x grinder - passed |
JDK22 x86-64_mac(
|
JDK23 x86-64_mac(
|
This has been deferred before, deferring it again. |
https://openj9-jenkins.osuosl.org/job/Test_openjdk21_j9_sanity.openjdk_x86-64_mac_OMR_testList_0/103
|
|
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk23_j9_sanity.openjdk_x86-64_mac_Release_testList_0/2 - mac12-x86-1a
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk21_j9_sanity.openjdk_x86-64_mac_Nightly_testList_0/224 - mac10-x86-2 https://openj9-artifactory.osuosl.org/artifactory/ci-openj9/Test/Test_openjdk21_j9_sanity.openjdk_x86-64_mac_Nightly_testList_0/224/openjdk_test_output.tar.gz |
https://openj9-jenkins.osuosl.org/job/Test_openjdk23_j9_sanity.openjdk_x86-64_mac_Nightly_testList_0/16/ - mac14-x86-3a
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk21_j9_sanity.openjdk_x86-64_mac_OpenJDK21_testList_1/26/ - mac10-x86-1
|
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk21_j9_sanity.openjdk_x86-64_mac_OpenJDK21_testList_1/27
|
|
I looked at the last reported crash. I got some backtrace in lldb but it's missing symbols from The backtrace from the console
The backtrace from lldb
It crashes in The I looked at how [1]
[2]
===
[3]
|
I'm trying to capture some debugging information from earlier iterations of the stack walk in hopes of being able to reconstruct how we get to the point of failure. My first grinder run showed no failures. Trying again. . . . |
I suspect that the thread whose stack is being walked might still be running, and that that is messing up the stack walking. I added some debugging code into Using lldb to look at one of the core files captured in https://na.artifactory.swg-devops.com/artifactory/sys-rt-generic-local/hyc-runtimes-jenkins.swg-devops.com/Grinder_iteration_3/3406/openjdk_test_output.tar.gz:
The assignment of @tajila, could someone on the VM team help investigate this further? |
@babsingh Can you please take a look at this? |
I looked at the most recent core file from #18910 (comment). There is only one virtual thread. It is being unmounted. As per #17303, there should be a retry (
|
I also looked at the core file which was inspected by @hzongaro in #18910 (comment). In this case, the virtual thread is being mounted. In both cases, the virtual thread is in an unsteady state (either being mounted or unmounted). This is indicated by
|
re #18910 (comment) and #18910 (comment): There is a very unlikely code path where the continuation is already detached but the carrierThread have not been reset on the Vthread, by the time reaching check in #17303. I didn't see any reason for the mount case to fail though as that work differently since the mount process is guarded more. |
If inspectorCount is -1, then the virtual thread is in an unsteady state (mounting or unmounting). In such cases, NULL should be returned and the JCL code should retry in order to avoid unexpected behavior. Related: eclipse-openj9#18910 Signed-off-by: Babneet Singh <[email protected]>
If inspectorCount is -1, then the virtual thread is in an unsteady state (mounting or unmounting). In such cases, NULL should be returned and the JCL code should retry in order to avoid unexpected behavior. Related: eclipse-openj9#18910 Signed-off-by: Babneet Singh <[email protected]>
If inspectorCount is -1, then the virtual thread is in an unsteady state (mounting or unmounting). In such cases, NULL should be returned and the JCL code should retry in order to avoid unexpected behavior. Related: eclipse-openj9#18910 Signed-off-by: Babneet Singh <[email protected]>
Issue Number: 18910 |
If inspectorCount is -1, then the virtual thread is in an unsteady state (mounting or unmounting). In such cases, NULL should be returned and the JCL code should retry in order to avoid unexpected behavior. Related: eclipse-openj9#18910 Signed-off-by: Babneet Singh <[email protected]>
If inspectorCount is -1, then the virtual thread is in an unsteady state (mounting or unmounting). In such cases, NULL should be returned and the JCL code should retry in order to avoid unexpected behavior. Related: eclipse-openj9#18910 Signed-off-by: Babneet Singh <[email protected]>
If inspectorCount is -1, then the virtual thread is in an unsteady state (mounting or unmounting). In such cases, NULL should be returned and the JCL code should retry in order to avoid unexpected behavior. Related: eclipse-openj9#18910 Signed-off-by: Babneet Singh <[email protected]>
https://openj9-jenkins.osuosl.org/job/Test_openjdk22_j9_sanity.openjdk_x86-64_mac_Nightly_testList_1/1
jdk_lang_1
java/lang/Thread/virtual/stress/GetStackTraceALotWhenPinned.java#id0
https://openj9-artifactory.osuosl.org/artifactory/ci-openj9/Test/Test_openjdk22_j9_sanity.openjdk_x86-64_mac_Nightly_testList_1/1/openjdk_test_output.tar.gz
The text was updated successfully, but these errors were encountered: