-
Notifications
You must be signed in to change notification settings - Fork 28.7k
Guard against usage after async callbacks in RenderAndroidView, unregister listener #108496
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
Conversation
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.
Looks like a mock in another test needs updating, but otherwise LGTM. Thanks for investigating this!
We should definitely cherry-pick this to beta
(and maybe even stable
?).
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.
LGTM
|
Is the flutter_plugins failure a known issue? Looks like mockito deprecated something that plugins is using? |
/cc @Piinks Is this the same issue that turned the tree red? |
Yeah it is the same failure that has the tree red |
…w, unregister listener (flutter/flutter#108496)
…w, unregister listener (flutter/flutter#108496)
…108831) * Guard against usage after async callbacks in RenderAndroidView, unregister listener (#108496) * Roll flutter/plugins (#108556) Co-authored-by: Dan Field <[email protected]> Co-authored-by: stuartmorgan <[email protected]>
xref b/186978412
When this code was written, render object disposal wasn't a thing. When I implemented that, I didn't realize there were async methods being used in this render object.
The test in this patch is basically a clone of an existing test, but it disposes the RO before completing some of the async operations. Without the changes in the implementation the test fails.