Maximum RTCDataChannels in Chrome

Clash Royale CLAN TAG#URR8PPP
Maximum RTCDataChannels in Chrome
Mozilla MDN states that a single RTCPeerConnection can handle "in theory" 65,534 data channels yet states that the limit will vary browser to browser. I haven't been able to find documentation as to the maximum RTCDataChannels allowed in Chrome.
2 Answers
2
Chrome announces 1024 outgoing streams and uses the usrsctp default of 2048 incoming streams.
For comparison, Firefox announces 256 outgoing streams and 2048 incoming streams but allows to renegotiate for up to 2048 streams. However, there is a bug in the renegotiation procedure.
One of the peer takes odd stream IDs and the other takes even stream IDs to create a data channel (which avoids conflicts if both peers create data channels at the same time). The result is that you can create half as many data channels per peer as the amount of streams that have been negotiated (minimum of both).
Data channels can also be created in a way where you assign the id yourselves in which case you can create as many data channels as the negotiated amount of streams.
The limit of what exactly?
– Lennart Grahl
Aug 13 at 10:54
software Engineer Lennart Grahl took some tests about maximum RTCDataChannels in chrome and
firefox,so can read about it at this link
https://lgrahl.de/articles/demystifying-webrtc-dc-size-limit.html
By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.
What's the limit that you've found in rawrtc?
– JSON
Aug 7 at 15:23