On 7/23/2013 9:02 AM, [email protected] wrote:
Hi,
What is the proper way of closing a WebRTC dataChannel? We are developing a p2p
file-sharing webapp, and seem to hit a global limit for number of dataChannels
if the app runs for a long time.
Currently we do a dataChannel.close() and a peerConnection.close(), as well as
setting the references of both to null. Is there anything else that needs to be
done for the dataChannel to be properly garbage collected?
channel.close() and dropping all pointers to it is all that should be
needed. Also, channels are per-peerconnection, and we auto-negotiate
use of more channels as needed (up to 32K opened from each side).
You could try running a test with a debug nightly build (from
ftp.mozilla.org) and set NSPR_LOG_MODULES=datachannel:5 and
NSPR_LOG_FILE=something. Note: there will be a lot of debugs. When it
fails, near the end of the (long) logs there should be an error, or at
least info that can be used.
Please get the info and file a bug with the tail meg or so from the
logs. Use Core, component WebRTC Networking.
Thanks!
--
Randell Jesup, Mozilla
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
