[release/6.0] [iOS][Android] Fix crash in Exception.CaptureDispatchState #71171
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #70970 to release/6.0
/cc @steveisok
Customer Impact
There exists a race condition in mono's implementation of
Exception.CaptureDispatchState
that can cause a crash when an exception is re-thrown from anawait
from multiple observers. The crash happens whenException.RestoreDispatchState
is called at the same timeException.CaptureDispatchState
is and anArray.Copy
fails due to an internal member length change.This is impacting a customer that is trying to move over to MAUI, but can't due to this issue.
Testing
Manual testing of a customer provided reproduction
Risk
Low - the change captures the shared state in a local variable so that
Exception.CaptureDispatchState
can do its jobIMPORTANT: If this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.