Fix crashes when BLE rendezvous disconnects unexpectedly #4413
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.
In BLE::OnBleEndPointConnectionClosed, the endpoint is already closed.
We try to close it again in the Transport::BLE destructor, which can crash.
Clear the endpoint in OnBleEndPointConnectionClosed to avoid this case.
In addition, the OnRendezvousError callback in the typical case stops
the rendezvous process which immediately destroys the transport. We
therefore can't call OnRendezvousConnectionClosed afterwards; |this| is
already freed and we just need to return.