-
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
Random crashes in System.Net.Mail test suites with mono interpreter #87271
Comments
Tagging subscribers to this area: @BrzVlad, @kotlarmilos Issue DetailsDescriptionThis happens often on CI: To reproduce:
Environment:
Reproduction Steps. Expected behavior. Actual behavior. Regression?No response Known WorkaroundsNo response ConfigurationNo response Other informationNo response
|
|
Looks like |
I get random crashes inside the interpreter locally:
|
The way this issue reproduces is that when doing a call The following fix solves the issue:
Adding a read barrier in the fast path for each call might be quite expensive. It might be worthwhile benchmarking though. Another possible fix would be to rely on data dependency to ensure data is accessed correctly. We could extract imethod compilation data in a separate structure that is published in the imethod when compilation is done and then, during method execution, access this through it: Another fix that would add no overhead for calls, would be to reuse the existing idea used for tiering and patch with new imethods. We would have a separate |
Wouldn't getting rid of |
The same logical problem still remains, that if the method is transformed we expect certain fields to have been properly initialized. We could check for |
Description
This happens often on CI:
https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-f9cccf963c964959af/System.Net.Mail.Functional.Tests/1/console.a97473cd.log?helixlogtype=result
To reproduce:
Environment:
Reproduction Steps
.
Expected behavior
.
Actual behavior
.
Regression?
No response
Known Workarounds
No response
Configuration
No response
Other information
No response
Known Issue Error Message
Fill the error message using step by step known issues guidance.
Report
Summary
The text was updated successfully, but these errors were encountered: