You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When RTCDataChannel: close() method on a JS client (Chrome for example) the data channel hangs in closing state and never transitions to closed.
This causes a memory leak and eventually more data channels cannot be created with the following error:
Uncaught (in promise) DOMException: Failed to execute 'createDataChannel' on 'RTCPeerConnection': RTCDataChannel creation failed
Reproduction
Using the examples/data-channels
Run the JS test for closing data channels: jsfiddle
Note the RTCDataChannel never enters closed state.
Possible cause
I suspect the issue here is with webrtc-rs not replying with a stream reset to the browsers request to close the stream. I see the spec referenced here but am not sure if it's working correctly.
The text was updated successfully, but these errors were encountered:
Problem
When RTCDataChannel: close() method on a JS client (Chrome for example) the data channel hangs in
closing
state and never transitions toclosed
.This causes a memory leak and eventually more data channels cannot be created with the following error:
Reproduction
Using the examples/data-channels
Run the JS test for closing data channels: jsfiddle
Note the RTCDataChannel never enters
closed
state.Possible cause
I suspect the issue here is with
webrtc-rs
not replying with a stream reset to the browsers request to close the stream. I see the spec referenced here but am not sure if it's working correctly.The text was updated successfully, but these errors were encountered: