-
Notifications
You must be signed in to change notification settings - Fork 712
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
Segmentation error vmState=0x00053cff #15730
Comments
@0xdaryl fyi |
|
@mateuszrzeszutek, is the test system able to capture a core file? Failing that, is there any way I could reproduce the problem in a stand-alone way? And if not, I'm wondering if you might be able to capture the bytecode for |
Ignore that - I guess it's not being instrumented |
@mateuszrzeszutek, if capturing a core file is not easy to do, are you easily able to rerun the affected test with the following additional JIT compiler options? That might help shed more light on the problem.
|
We won't get to the bottom of this for 0.35. Moving to 0.36. |
Hello @mateuszrzeszutek. I was wondering whether you have had any success in attempting to capture any trace logs or core files. They would be a great help in trying to resolve this problem. |
Hey, |
Hi @mateuszrzeszutek. Have you had any luck producing core files or log files? |
Hi, @mateuszrzeszutek. I just wanted to follow up to see whether you were able to produce any core files or log files for this problem. It will be difficult to figure out what might be going wrong without them. |
Moving to 0.38 release. |
Hi, @mateuszrzeszutek. I wanted to follow up again to see whether you're still seeing this problem and whether you might be able to gather any core or log files to help us investigate the cause of the crash. |
Since I haven't heard from the originator of this problem recently, I spent a little bit of time digging into the jitdump file again, jitdump.20220816.133744.23602.0004.dmp.txt In the version of IBM Semeru that's involved, the bytecode for
The failure seems to occur in an AOT compilation. In the IL that's shown in the jitdump, we see this.
I believe the Putting that aside for now, IL generation is generating inline code for the call to I spent some time trying to reproduce the failure, but I'm hitting this AOT error:
In the original jitdump, this AOT message appears for the recompilation:
I will spend some more time trying to piece together how we might come to generate that IL. |
Moving to 0.40. |
I'm going to move this to the Backlog. I strongly suspect the problem still exists, but we haven't been able to reproduce it, and the originator hasn't reported any further occurrences of the problem, which hampers investigation. |
Fixed by #19604 I think |
Java -version output
Summary of problem
The OpenTelemetry Java Instrumentation builds have recently started randomly failing on JIT compilation in the Java 18 openj9 build.
Diagnostic files
You can find the diagnostic files attached to the GHA build: https://github.com/open-telemetry/opentelemetry-java-instrumentation/actions/runs/2867509938 in the javacore-test-18 artifact.
In case you need more examples, this has happened several times in our daily build job: https://github.com/open-telemetry/opentelemetry-java-instrumentation/actions/runs/2865361522, https://github.com/open-telemetry/opentelemetry-java-instrumentation/actions/runs/2858576759
The text was updated successfully, but these errors were encountered: