Duplicate of #110350 . cc @VSadov

@Sergio0694 Could you please validate that it is fixed in 9.0.5?

(backport PR #113055)

Oh that's nice! I can try, yes, though it might be slightly tricky as I can't repro this myself.
Just to confirm, is this only affecting CoreCLR, or does this affect Native AOT as well?

Yes, this looks like #110350 . The fix has been backported to 9.0, but may not be available till the next servicing release.
As Jan suggested - it would be very helpful if you could try with 9.0.5 bits (i.e. #113055)

Just to confirm, is this only affecting CoreCLR, or does this affect Native AOT as well?

It does not affect Native AOT. The fix was to switch regular CoreCLR to how Native AOT works.

Perfect, thank you for confirming! At least we know this only affects our dev inner loop then 🙂

NativeAOT had a remotely related issue, fixed in #113194

But that is related to COM and is pretty hard to observe, even intentionally.
It would not show up as a deadlock though. In fact, in most cases it would not have any adverse effects, so is unlikely to bother you.

I assume I can test the fix by installing the latest nightly SDK from the 9.0 branch from the SDK repo?

Yes, you can do that if you do not want to wait for official release.

This issue has been marked needs-author-action and may be missing some important information.

This issue has been automatically marked no-recent-activity because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will remove no-recent-activity.

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.