-
Notifications
You must be signed in to change notification settings - Fork 446
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
fix: close webrtc streams without data loss #2073
Merged
Merged
Conversation
This file contains 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
achingbrain
force-pushed
the
fix/webrtc-stream-closing
branch
from
September 23, 2023 20:14
5e47bff
to
005ddbf
Compare
achingbrain
changed the title
fix: close webrtc streams
fix: wait for webrtc stream buffers to empty before closing
Sep 23, 2023
This was referenced Oct 1, 2023
@achingbrain is this ready for review? |
@wemeetagain yes! |
maschad
reviewed
Oct 4, 2023
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.
Looks good so far, left some comments.
Chrome does not always send all messages after closing a datachannel even if `bufferedAmount` is `0` before closing. This PR adds a `FIN_ACK` message that is sent in reply to a `FIN` message - because all messages are send in-order, when this is received we know the remote has received all of our data messages and it's safe to close the channel.
wemeetagain
reviewed
Oct 5, 2023
maschad
approved these changes
Oct 5, 2023
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.
Great job on this, one minor comment. lgtm
Co-authored-by: Chad Nehemiah <chad.nehemiah94@gmail.com>
achingbrain
changed the title
fix: wait for webrtc stream buffers to empty before closing
fix: close webrtc streams without data loss
Oct 6, 2023
achingbrain
added a commit
that referenced
this pull request
Oct 6, 2023
- Gracefully close streams on muxer shutdown - Refactor initiator/recipient flows for clarity - Wait for `bufferedAmount` to be `0` before closing a datachannel - Close datachannels on both initiator and recipient - Implements FIN_ACK for closing datachannels without data loss Supersedes #2048 --------- Co-authored-by: Chad Nehemiah <chad.nehemiah94@gmail.com>
This was referenced Oct 10, 2023
This was referenced Jan 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
bufferedAmount
to be0
before closing a datachannelSupersedes #2048
Depends on: