W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2014

Re: [Bug 25724] New: Allow garbage collection of closed PeerConnections

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Fri, 16 May 2014 06:29:49 +0000
To: "bugzilla@jessica.w3.org" <bugzilla@jessica.w3.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B1CFE55C3@ESESSMB209.ericsson.se>
On 2014-05-15 12:22, bugzilla@jessica.w3.org wrote:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=25724
>
>              Bug ID: 25724
>             Summary: Allow garbage collection of closed PeerConnections
>             Product: WebRTC Working Group
>             Version: unspecified
>            Hardware: PC
>                  OS: Linux
>              Status: NEW
>            Severity: normal
>            Priority: P2
>           Component: WebRTC API
>            Assignee: public-webrtc@w3.org
>            Reporter: harald@alvestrand.no
>                  CC: public-webrtc@w3.org
>
> At the moment, the webrtc specification says:
>
> 4.3.3 Garbage collection
>
> A Window object has a strong reference to any RTCPeerConnection objects created
> from the constructor whose global object is that Window object.
>
> In other words, RTCPeerConnections can't be garbage collected.

I think this was originally done on purpose. The app should be able to 
wire up a PeerConnection with a video element, and drop all references 
but continue to have the (from remote coming) video being rendered.

The side effect when many connections are created and dropped was not 
foreseen, so I'm all for making this change.
Received on Friday, 16 May 2014 06:30:15 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:40 UTC