-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[.NET 7.0 + WASM AOT] Assembly.GetName().Name crashes the app #79814
Comments
This is a testcase which is supposed to hit the relevant code path:
However, it doesn't cause a crash with dotnet/runtime HEAD. |
@vargaz thanks for looking into. Curious: I don't see What am I missing? |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsDescription@vargaz I came across another WASM AOT crash where @jeromelaban pointed me here. I'll copy the details of my original report for your convenience ... and please believe me, for the whole weekend I (successfully) isolated the issue in my app and (unsuccessfully) tried to create a repo, but again failed ... so, again no repo :-( I isolated an AOT crash where adding the line Interestingly I have the line below right before the offending line above in my code and this itself does not cause any issues And it's getting even more weird: if I commented out the offending line, then the app would work as expected - of course. But if I 'commented' it out by
... then the app still would crash?!? Really?!? Go figure... Unfortunately I was unable to create a repo - although the issue itself is 100% reproducible by only adding the offending line above to my app. So, another WASM AOT mystery ... :-( Would you have any idea idea what might be causing the issue?
Reproduction StepsPlease see above Expected behaviorPlease see above Actual behaviorPlease see above Regression?No response Known WorkaroundsNone ConfigurationNo response Other informationNo response
|
The testcase should hit the code path inside the runtime which contains the failed assertion. Unfortunately, it doesn't reproduce the problem for me. |
@vargaz thanks again. Is there anything else I could try to isolate the issue (although every iteration will take ~1 hour due to the time needed to do the AOT build)? |
If you add the testcase code to the app, does it cause it to crash ? |
@vargaz thanks for getting back to me. Please find below what I see when adding your code above to my app and executing it like:
Does this help? |
Does it also fail if you add the testcase to an empty uno app ? |
Also, can you try to get a verbose build log (/v:d argument to msbuild) ? |
@vargaz that's interesting: I can't compile a blank UNO template using your code since there is conflict on static 'Main' function. Even if I stuffed your code in a different namespace would it not compile. @jeromelaban FYI So, I renamed 'Main' to 'Run'. However, the AOT compilation of a blank UNO project would not crash. |
…cmod. The wrappers are not found at runtime in some cases. Ref: dotnet#79814.
…cmod. The wrappers are not found at runtime in some cases. Ref: #79814.
…cmod. (#81003) The wrappers are not found at runtime in some cases. Ref: #79814. Co-authored-by: Zoltan Varga <[email protected]>
Description
@vargaz I came across another WASM AOT crash where @jeromelaban pointed me here.
I'll copy the details of my original report for your convenience ... and please believe me, for the whole weekend I (successfully) isolated the issue in my app and (unsuccessfully) tried to create a repo, but again failed ... so, again no repo :-(
I isolated an AOT crash where adding the line
var o = GetType().Assembly.GetName().Name;
... to my app's code crashes the app (screenshow and logs below).
Interestingly I have the line below right before the offending line above in my code and this itself does not cause any issues
collection-which-is-not-empty.FirstOrDefault(o => o.Name == assembly.GetName().Name && o.Version == assembly.GetName().Version.ToString(3)) == null
And it's getting even more weird: if I commented out the offending line, then the app would work as expected - of course. But if I 'commented' it out by
... then the app still would crash?!? Really?!? Go figure...
Unfortunately I was unable to create a repo - although the issue itself is 100% reproducible by only adding the offending line above to my app. So, another WASM AOT mystery ... :-(
Would you have any idea idea what might be causing the issue?
1671438561270.zip
Reproduction Steps
Please see above
Expected behavior
Please see above
Actual behavior
Please see above
Regression?
No response
Known Workarounds
None
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: