-
Notifications
You must be signed in to change notification settings - Fork 6k
Add missing cancellable to text input handler #56666
Add missing cancellable to text input handler #56666
Conversation
Without this if a channel method call was in progress and then the handler was destroyed the call could attempt to access the destroyed handler. This is possible as the handler is recreated on engine restart. However, in this case the result is not used so no invalid memory access would occur. Adding the cancellable fixes any future change where this would no longer be the case.
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group. |
|
test-exempt: code refactor with no semantic change |
cbracken
left a comment
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.
…159134) flutter/engine@983b7b8...b6723e3 2024-11-19 [email protected] Roll Skia from 17601e471acf to 8a1a84509501 (4 revisions) (flutter/engine#56700) 2024-11-19 [email protected] Roll Skia from 8d652f142911 to 17601e471acf (1 revision) (flutter/engine#56696) 2024-11-19 [email protected] Add missing cancellable to text input handler (flutter/engine#56666) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll Please CC [email protected],[email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Without this if a channel method call was in progress and then the handler was destroyed the call could attempt to access the destroyed handler. This is possible as the handler is recreated on engine restart. However, in this case the result is not used so no invalid memory access would occur. Adding the cancellable fixes any future change where this would no longer be the case.

Without this if a channel method call was in progress and then the handler was destroyed the call could attempt to access the destroyed handler. This is possible as the handler is recreated on engine restart.
However, in this case the result is not used so no invalid memory access would occur. Adding the cancellable fixes any future change where this would no longer be the case.