Issue metadata
Sign in to add a comment
|
bluetooth: windows: Call error callbacks upon object destruction. |
||||||||||||||||||||||
Issue description
Several classes retain callbacks while asynchronous operations are pending. In the event of the instances being destroyed the callbacks are not called, but they should be.
E.g.
BluetoothRemoteGattCharacteristicAndroid::
~BluetoothRemoteGattCharacteristicAndroid() {
...
if (pending_start_notify_calls_.size()) {
OnStartNotifySessionError(device::BluetoothGattService::GATT_ERROR_FAILED);
}
}
,
Oct 6 2016
,
Oct 6 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by scheib@chromium.org
, Mar 25 2016