W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > July 2017

Re: [webrtc-pc] Limiting number of RTCRtpTransceivers

From: Mark Roberts via GitHub <sysbot+gh@w3.org>
Date: Tue, 25 Jul 2017 06:14:34 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-317640136-1500963272-sysbot+gh@w3.org>
@stefhak yeah, my first question is fairly generic/obvious. I too assume there is a limit. I'm actually interested in the follow-on questions.

Although JSEP specifies that we can reuse a stopped RTCRtpTransceiver's m= section, there isn't a similar behavior at the WebRTC layer for "freeing" stopped RTCRtpTransceivers. AFAICT, if I have some long-lived application calling `addTransceiver`/`stop` or `addTrack`/`removeTrack` I will just keep accumulating RTCRtpTransceivers at the WebRTC layer, even if JSEP is keeping my m= sections tidy. This feels especially strange to me if the application follows each call to `addTrack` with `removeTrack`, since—reading the APIs alone—you might not suspect they leak a resource (the RTCRtpTransceiver).

Can this or should this be changed? E.g., by removing stopped RTCRtpTransceivers from the RTCPeerConnection's set of transceivers? By reusing RTCRtpSenders in more scenarios?

GitHub Notification of comment by markandrus
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1507#issuecomment-317640136 using your GitHub account
Received on Tuesday, 25 July 2017 06:14:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:21:40 UTC