-
Notifications
You must be signed in to change notification settings - Fork 736
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
JDK11 Linux ppc64le java/util/Hashtable/SerializationDeadlock.java *** stack smashing detected *** #10630
Comments
Changes from the previous build: @andrewcraik @r30shah could this be caused by #10366 ? |
@pshipton Let me take a look. |
@pshipton Looking into core-dump, I think this failure is not related to the #10366 as On the stack I am seeing,
So it is more likely related to eclipse-omr/omr#5219 and hitting ASSERT at https://github.com/eclipse/omr/blob/25e93bed006afa4333c1a1c5f6a9a24342da3ecc/compiler/optimizer/RegDepCopyRemoval.cpp#L441 I am trying to reproduce this locally/internally as core-dump/jitdump in the test does not provide more information. |
Would it be possible to launch a grinder of 100 runs on the Eclipse CI ? I ran the test internally on PPCLE 64 machine for 100 runs but can not reproduce the failure, if we can get it fairly reproducible, then I would have to get access to the external machine to continue investigation. |
I launched 2 grinders, one on the same machine where it originally failed. Started more |
None of the grinders from #10630 (comment) had failures (0/420). |
Can we update the assert to provide more information in case the problem occurs again? |
Let me see, currently it provides information about the node that was encountered but not expected (Information contains node index and opcode). I think this kind of failure would benefit most from good jitdump. I see in the stack trace in https://ci.eclipse.org/openj9/job/Test_openjdk11_j9_sanity.openjdk_ppc64le_linux_xl_Nightly/148/consoleFull , it was in middle of processing the jitdump and fails. Looked through the jitdump from the failure, tree looked OK ( I can not find any incorrect GlRegDeps). |
@r30shah yes this failure generated a useful jitdump showing a clear error:
You can find the jitdump in the Artifacts safed on the build:
|
By the way @r30shah we should use |
@fjeremic Yes, checked it again with the context of #10671 where I did see the ASSERT message as well which is missing from this failure. But I can verify that the node in question pointed by the |
Fix the assert added in RegDepCopyRemoval to consider missing case where child of GlRegDeps is PassThrough with the regLoad child and both uses same register. Fixes: eclipse-openj9/openj9#10630 Signed-off-by: Rahil Shah <[email protected]>
@pshipton Wanted to verify if we can deliver this in 0.23 branch, I will open PR against it. |
Fix the assert added in RegDepCopyRemoval to consider missing case where child of GlRegDeps is PassThrough with the regLoad child and both uses same register. Fixes: eclipse-openj9/openj9#10630 Signed-off-by: Rahil Shah <[email protected]>
@r30shah Pls cherry pick the change against https://github.com/eclipse/openj9-omr/tree/v0.23.0-release and let me know the PR #. |
Thanks @pshipton , here is the PR eclipse-openj9/openj9-omr#79 |
Fix the assert added in RegDepCopyRemoval to consider missing case where child of GlRegDeps is PassThrough with the regLoad child and both uses same register. Fixes: eclipse-openj9/openj9#10630 Signed-off-by: Rahil Shah <[email protected]>
Failure link
https://ci.eclipse.org/openj9/job/Test_openjdk11_j9_sanity.openjdk_ppc64le_linux_xl_Nightly/148/consoleFull
Optional info
Failure output (captured from console output)
The text was updated successfully, but these errors were encountered: