WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED WONTFIX
121103
RTCPeerConnection objects must have the same lifetime as Window
https://bugs.webkit.org/show_bug.cgi?id=121103
Summary
RTCPeerConnection objects must have the same lifetime as Window
Eric Carlson
Reported
2013-09-10 11:09:44 PDT
Consider merging
https://chromium.googlesource.com/chromium/blink/+/d2c15b9a56ace790cbf0e71507034ebd64da0ff6
The spec states that: "A Window object has a strong reference to any RTCPeerConnection objects created from the constructor whose global object is that Window object." Which means that RTCPC objects should never be garbage collected.
Attachments
Add attachment
proposed patch, testcase, etc.
Sam Weinig
Comment 1
2013-09-10 16:07:07 PDT
That's a bit mysterious. What is the observable symptom this bug fixes?
Eric Carlson
Comment 2
2013-09-13 13:20:41 PDT
(In reply to
comment #1
)
> That's a bit mysterious. What is the observable symptom this bug fixes?
I asked Adam Bergkvist, one of the spec authors, about that section of the spec and he said: The RTCPeerConnection Garbage Collection section doesn't make sense to me either. I don't think that particular section has been touched since the w3c forked the WHATWG WebRTC spec. My initial thinking is that the RTCPeerConnection object should be protected when certain listeners are attached; similar to RTCDataChannel [1] (which mimics WebSocket). So I am marking this as WONTFIX and we can revisit the issue when the spec is updated.
Sam Weinig
Comment 3
2013-09-13 13:28:55 PDT
(In reply to
comment #2
)
> (In reply to
comment #1
) > > That's a bit mysterious. What is the observable symptom this bug fixes? > > I asked Adam Bergkvist, one of the spec authors, about that section of the spec and he said: > > The RTCPeerConnection Garbage Collection section doesn't make sense to me either. > I don't think that particular section has been touched since the w3c forked the > WHATWG WebRTC spec. > > My initial thinking is that the RTCPeerConnection object should be protected when > certain listeners are attached; similar to RTCDataChannel [1] (which mimics WebSocket). > > So I am marking this as WONTFIX and we can revisit the issue when the spec is updated.
Just to throw a wrench in the mix, it looks like the blink patch doesn't actually do what it states, it looks like what it does is change things so RTCPeerConnections won't get GC'd while the connection is not stopped. We may want that behavior, but I am not sure.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug