-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
GC crash in .NET 9 UWP and WinUI 3 apps published with Native AOT on win-x86 #110607
Labels
Comments
Tagging subscribers to this area: @dotnet/gc |
👀 cc. @manodasanW |
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas |
MichalStrehovsky
added a commit
to MichalStrehovsky/runtime
that referenced
this issue
Dec 13, 2024
Fixes dotnet#110607. The native side expects fastcall. Filed dotnet#110684 on the test hole. We would have caught it during x86 bringup if this had _any_ tests since this is a guaranteed stack corruption and crash.
Thank you for the good repro! I have a PR out with a fix. |
MichalStrehovsky
added a commit
that referenced
this issue
Dec 16, 2024
4 tasks
Sergio0694
pushed a commit
to Sergio0694/runtime
that referenced
this issue
Jan 7, 2025
Fixes dotnet#110607. The native side expected fastcall, managed side didn't. Filed dotnet#110684 on the test hole. We would have caught it during x86 bringup if this had _any_ tests since this is a guaranteed stack corruption and crash.
jeffschwMSFT
added a commit
that referenced
this issue
Jan 8, 2025
…111105) * Fix calling convention mismatch in GC callouts Fixes #110607. The native side expects fastcall. Filed #110684 on the test hole. We would have caught it during x86 bringup if this had _any_ tests since this is a guaranteed stack corruption and crash. * Change native side instead --------- Co-authored-by: Michal Strehovský <MichalStrehovsky@users.noreply.github.com> Co-authored-by: Jeff Schwartz <jeffschw@microsoft.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Description
I am migrating an UWP applicaiton to .NET 9 and found a problem with win-x86 Native AOT publish. The app works when it's either unpackaged or published using win-x64 runtime. But when it's published using win-x86 runtime, gc crashes on random instructions when trying to collect memory. Example stack trace from crash dump:
The same problem is reproduced for both WinUI 3 and UWP apps, but not reproduces for console application.
Reproduction Steps
It's reproducible on both UWP and WinUI 3, but for simplicity specifying WinUI 3 here.
Expected behavior
App launches and runs.
Actual behavior
App crashes with stacktrace specified in descripiton.
Regression?
No, since x86 is available in .NET 9 only.
Known Workarounds
No response
Configuration
Dotnet info:
Windows SDKs installed;
Other information
Repo with reproduction examples: https://github.com/andrew-kulikov/native-aot-test
The text was updated successfully, but these errors were encountered: