You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a DeviceCommissioner is shut down while in the middle of doing BLE discovery for a commissioning attempt, we may end up with use-after-free, because some of our platforms don't have an obvious way to cancel BLE discovery, and when it calls back it will be touching deleted objects.
Proposed Solution
Figure out whether we can tie the BLE discovery handling to something that has long-enough lifetime and holds weak refs to the SetUpCodePairer that get nulled out as needed, or whether we can make BLE discovery be consistently cancelable.
The text was updated successfully, but these errors were encountered:
Problem
If a DeviceCommissioner is shut down while in the middle of doing BLE discovery for a commissioning attempt, we may end up with use-after-free, because some of our platforms don't have an obvious way to cancel BLE discovery, and when it calls back it will be touching deleted objects.
Proposed Solution
Figure out whether we can tie the BLE discovery handling to something that has long-enough lifetime and holds weak refs to the SetUpCodePairer that get nulled out as needed, or whether we can make BLE discovery be consistently cancelable.
The text was updated successfully, but these errors were encountered: