-
Notifications
You must be signed in to change notification settings - Fork 255
chore: bump flutter_webrtc to 1.6.2+hotfix.2 #1203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+4
−3
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| patch type="changed" "Bump flutter_webrtc to 1.6.2+hotfix.2" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
🔴 Desktop teardown leaks peer connections
On Windows and Linux,
flutter_webrtcnow requires disposal before close, butTransportkeeps the reverse order. The first close removes the native lookup entry, so disposal cannot release its observer. Each teardown retains a peer connection and observer, accumulating native resources across reconnects.Learn more
The upgraded desktop implementation splits teardown across two platform calls.
peerConnectionDisposecloses the native connection while its observer remains alive, unregisters that observer, and leaves the connection map entry forpeerConnectionCloseto remove. Transport disposal sends those calls in the opposite order. The first call removes the map entry, so the second call returns without reaching observer teardown. The observer owns a reference to the native peer connection, leaving both allocated.Example: A Windows client reconnects ten times. Each old publisher and subscriber transport calls
close()beforedispose(). All twenty native observers and their peer connections remain retained instead of being released.Recommended fix: Reverse the calls in
Transportso it awaitspc.dispose()beforepc.close()on the affected implementation. Verify this ordering on every supported platform, then add a Windows/Linux teardown regression that exercises the SDK's actualTransportsequence.Was this helpful? React with 👍 or 👎 to provide feedback.