-
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
[release/7.0] [mono][interp] Add unbox when calling valuetype method through delegate #79614
[release/7.0] [mono][interp] Add unbox when calling valuetype method through delegate #79614
Conversation
If we are calling an open instance delegate, where the target method is on a valuetype, we will need to unbox this pointer.
Tagging subscribers to this area: @BrzVlad Issue DetailsIf we are calling an open instance delegate, where the target method is on a valuetype, we will need to unbox this pointer. Backport of #79445 Fixes #79354 Customer ImpactMAUI iOS applications making use of the popular TestingVerified fix on sample app provided in the bug report and created a simple test case that is included in our suite. RiskLow. The fix only touches the code path for a very specific type of delegate invocation pattern which was previously handled incorrectly before.
|
From the original PR, this doesn't contain the 846f4ea commit, since it is unnecessary risk for backport PR |
@carlossanlop - this is approved via Tactics email, but we should wait till @BrzVlad confirms the CI failures are not relevant. |
7ced39b
to
dc8a8aa
Compare
dc8a8aa
to
61d4333
Compare
I'm not seeing any failures with this |
Approved by Tactics (7.0.3). |
If we are calling an open instance delegate, where the target method is on a valuetype, we will need to unbox this pointer.
Backport of #79445
Fixes #79354
Customer Impact
MAUI iOS applications making use of the popular
AutoMapper
NuGet library can crash in debug builds. Workaround is to disable mono interpreter and implicitly hot reload. Other platforms using interpreter, like blazor wasm, can potentially hit this issue even in Release.Testing
Verified fix on sample app provided in the bug report and created a simple test case that is included in our suite.
Risk
Low. The fix only touches the code path for a very specific type of delegate invocation pattern which was previously handled incorrectly before.