I notice sometimes with my massive to massive broadcasting that I have peers run out of RTCPeerConnections but I close them properly. Sure enough webrtc-internals does not garbage collect and keeps traces till refresh.
This in return throws errors after some time. If a user AFKs they are eventually met with the error even in the lightest of conditions.
Not sure if I’m to re-use RTCPeerConnections or if I’m to refresh the user upon error but I found a few options that may help. If RTCPeerConnection is loaded via iFrame; upon iFrame closure the debugger is cleared and it’s as if you never had a limit but my small implementation did error somehow. So I ponder and inquire!
What do you guys to keep in the range of chromium’s 500 limit.