-
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
[release/8.0] Events for IL methods without IL headers #90844
Conversation
Dynamically generated methods like UnsafeAccessor functions are marked as IL, but don't contain an IL header. The lack of header is an indication the IL must be generated at runtime.
Co-authored-by: Tlakaelel Axayakatl Ceja <tlakaelel.ceja@microsoft.com>
This reverts changes from rc1 - #90818. |
The crash is triggered by combination when all of the following are true:
I do not think that this is RC1 blocking issue. @jeffschwMSFT ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approved. we can merge when ready
last changes for rc1 were late last week. so unless this is a main line issue, we should fix in rc2 |
@jkotas or @jeffschwMSFT The CI is green, please merge when convenient. |
/backport to release/8.0-rc1 |
Started backporting to release/8.0-rc1: https://github.com/dotnet/runtime/actions/runs/6242340304 |
Backport of #90826 to release/8.0
/cc @AaronRobinsonMSFT
Customer Impact
This failure represents a potential crash when events are enabled. It is possible the process will crash randomly without this change.
Testing
The failure was predictable and occurred regularly (> 90 %) after a change to adopt it within the runtime.
Risk
Minimal. This is adding a null check in more places that already handle returning null.
IMPORTANT: If this backport is for a servicing release, please verify that:
The PR target branch is
release/X.0-staging
, notrelease/X.0
.If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.