-
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
Segmentation fault on linux after upgrading from .NET 8 to .NET 9 #110835
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
Thanks for the report! It is most likely still the same underlying issue as #109981, just manifesting in a different spot/under different conditions. Sadly there is no simple workaround in this case given the stack trace you shared, beyond disabling optimizations for the affected method. It might also be possible for me to build a .NET 9 version of the JIT that includes the fix, which you would then be able to test with by replacing libclrjit.so in your application folder with that version. Let me know if you're interested in that (and if so, what Linux version you are deploying on). |
Thanks for looking into that :-) If you can provide us the custom build of .NET 9 that would be the easiest for us. We are testing on |
You may be able to workaround this by disabling TieredPGO (set https://learn.microsoft.com/en-us/dotnet/core/runtime-config/compilation#profile-guided-optimization |
@karmeli87 I have attached a libclrjit.so that includes the fix for #109981 to your issue at https://developercommunity.visualstudio.com/t/Access-Violation-Exception-after-upgradi/10814326#T-N10815576. Can you please try your app with this JIT and see if it helps? |
Thanks! we will try it and let you know if it helps. I can confirm that setting |
Description
We recently upgraded from .NET 8 to .NET 9 and start to experience crashes in our tests with messages such as
We gathered a dump that was analyzed by MS team and they believe it to be a JIT bug (#110769 (comment))
It crashes at the last line of the code listed below because the finger2 is NULL:
I have gathered another dump with those env variables
to rule out hitting an already known issue #109981 with the suggested workaround (#109981 (comment))
Reproduction Steps
No minimal repro yet, but it happened all the time when we run our test suit on linux
Expected behavior
not to crash
Actual behavior
crashing
Regression?
Yes,
It was working fine on .NET 8
Known Workarounds
No response
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: