Re: [webrtc-pc] Limiting number of RTCRtpTransceivers

I think it would be reasonable to say that when a transceiver is stopped, and its m= section is recycled for another transceiver (meaning it's "not associated" with an m= section any more), it gets removed from the set of transceivers, since it's not needed by JSEP's algorithms any more.

But Dan's point about stats is that we already have another problem about memory use increasing indefinitely. Stats for deleted objects are kept around forever:

> The general rule is that stats objects, once created, exist for the lifetime of the PeerConnection that contains them, even when the underlying object they report on is stopped or deleted. This is important in order to report consistently on short-lived objects and to be able to report totals over the lifetime of a PeerConnection.

-- 
GitHub Notification of comment by taylor-b
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1507#issuecomment-319996489 using your GitHub account

Received on Thursday, 3 August 2017 15:04:12 UTC