fix: do ECClient disconnect in RTCIceConnectionStateClosed only to prevent crash. #75
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.
I found a bug that it crashes when I disconnect a room.
The bug is described in the issue I sent earlier: #74
I found the reason it crashes is that a block inside ECClient is being released when the ECClient is released(while ECRoom's
publishingStatsTimer
released, and so that ECRoom and ECClient are released).So I move the
disconnect
to RTCIceConnectionStateClosed to prevent this crash.And after I read the references addressed in this issue (#73), I still didn't find the answer that should both
RTCIceConnectionStateDisconnected
andRTCIceConnectionStateClosed
dodisconnect
. Since disconnect deallocatesECRoom
, and it "probably" always callsRTCIceConnectionStateClosed
, we could safely calldisconnect
atRTCIceConnectionStateClosed
.