-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[mono] AOT-llvm arm64 Performance runs crashing since 2024/09/30 #109220
Comments
@radekdoulik Do you think #107462 could have caused these crashes? |
Tagging subscribers to this area: @lambdageek, @steveisok |
Apparently this warning emits something: runtime/src/mono/mono/metadata/icall.c Line 1639 in 42c1be2
So we're failing to get the calling assembly name from the stack crawl mark or from the LMF. As a result we pass null for both Is there something different about stack walks on this lane? |
@radekdoulik might be related to the LLVM bump? |
Also weird we're looking for a type called |
This can help with dotnet#109220
if the range is correct, then it shouldn't be the bump. let see if using sync unwind tables on all arm64 targets will help #109406. I will take closer look if it doesn't help. @matouskozak IIRC you mentioned that you will be modifying CI to exercise this path. do you have PR around for that? |
The arm64 AOT/fullAOT CI is broken currently, we're trying to get it running but I don't have ETA yet. |
I believe this is no longer failing after #109406. |
Build Information
Build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2550314
Build error leg or test failing: Performance linux arm64 release mono AOT micro_mono perfampere
Runtime range: e690777...d024a5b
Performance range: dotnet/performance@b0debbd...7c3ed5d
Stack trace:
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng/internal/_build/results?buildId=2550314
Error message validated:
[at System.RuntimeTypeHandle:internal_from_name
]Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 10/25/2024 12:22:41 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: