[html5] r6163 - [giow] (0) Avoid salvaging documents that have active PeerConnections. (Maybe we [...]

whatwg at whatwg.org whatwg at whatwg.org
Tue May 31 15:47:20 PDT 2011


Author: ianh
Date: 2011-05-31 15:47:19 -0700 (Tue, 31 May 2011)
New Revision: 6163

Modified:
   complete.html
   index
   source
Log:
[giow] (0) Avoid salvaging documents that have active PeerConnections. (Maybe we should force close the PeerConnection objects, too?)

Modified: complete.html
===================================================================
--- complete.html	2011-05-31 22:37:16 UTC (rev 6162)
+++ complete.html	2011-05-31 22:47:19 UTC (rev 6163)
@@ -64425,6 +64425,17 @@
 
    </li>
 
+   <li>
+
+    <p>If the <code><a href=#document>Document</a></code>'s <code><a href=#window>Window</a></code> object <a href=#concept-peerconnection-owner title=concept-PeerConnection-owner>owns</a> any
+    <code><a href=#peerconnection>PeerConnection</a></code> objects whose
+    <a href=#peerconnection-readiness-state><code>PeerConnection</code> readiness state</a> is not
+    <code title=dom-PeerConnection-CLOSED><a href=#dom-peerconnection-closed>CLOSED</a></code>, then set
+    <code><a href=#document>Document</a></code>'s <var title=concept-document-salvageable>salvageable</var> state to
+    false.</p>
+
+   </li>
+
    <li><p>If the <code><a href=#document>Document</a></code>'s <var title=concept-document-salvageable>salvageable</var> state is
    false, empty the <code><a href=#document>Document</a></code>'s <code><a href=#window>Window</a></code>'s
    <a href=#list-of-active-timeouts>list of active timeouts</a> and its <a href=#list-of-active-intervals>list of active
@@ -75723,8 +75734,8 @@
 
   <h3 id=garbage-collection-0><span class=secno>9.6 </span>Garbage collection</h3>
 
-  <p>A <code><a href=#window>Window</a></code> object has a strong reference to any
-  <code><a href=#peerconnection>PeerConnection</a></code> objects created from the constructor
+  <p>A <code><a href=#window>Window</a></code> object <dfn id=concept-peerconnection-owner title=concept-PeerConnection-owner>has a strong reference</dfn> to
+  any <code><a href=#peerconnection>PeerConnection</a></code> objects created from the constructor
   whose global object is that <code><a href=#window>Window</a></code> object.</p> <!-- we
   could be less strict here, e.g. dropping the reference when there's
   no way for an event to be fired because there's no event handlers
@@ -75732,7 +75743,8 @@
   because no media is streaming; or e.g. dropping the reference when
   the object reaches the CLOSED state. But as dropping the reference
   in those cases is black-box indistinguishable from keeping the
-  reference, I haven't bothered to work out the exact rules. -->
+  reference, I haven't bothered to work out the exact rules. If you do
+  change this, see the /unloading document cleanup steps/. -->
 
 
   <h3 id=event-definitions-0><span class=secno>9.7 </span>Event definitions</h3>

Modified: index
===================================================================
--- index	2011-05-31 22:37:16 UTC (rev 6162)
+++ index	2011-05-31 22:47:19 UTC (rev 6163)
@@ -64417,6 +64417,17 @@
 
    </li>
 
+   <li>
+
+    <p>If the <code><a href=#document>Document</a></code>'s <code><a href=#window>Window</a></code> object <a href=#concept-peerconnection-owner title=concept-PeerConnection-owner>owns</a> any
+    <code><a href=#peerconnection>PeerConnection</a></code> objects whose
+    <a href=#peerconnection-readiness-state><code>PeerConnection</code> readiness state</a> is not
+    <code title=dom-PeerConnection-CLOSED><a href=#dom-peerconnection-closed>CLOSED</a></code>, then set
+    <code><a href=#document>Document</a></code>'s <var title=concept-document-salvageable>salvageable</var> state to
+    false.</p>
+
+   </li>
+
    <li><p>If the <code><a href=#document>Document</a></code>'s <var title=concept-document-salvageable>salvageable</var> state is
    false, empty the <code><a href=#document>Document</a></code>'s <code><a href=#window>Window</a></code>'s
    <a href=#list-of-active-timeouts>list of active timeouts</a> and its <a href=#list-of-active-intervals>list of active
@@ -75738,8 +75749,8 @@
 
   <h3 id=garbage-collection-0><span class=secno>9.6 </span>Garbage collection</h3>
 
-  <p>A <code><a href=#window>Window</a></code> object has a strong reference to any
-  <code><a href=#peerconnection>PeerConnection</a></code> objects created from the constructor
+  <p>A <code><a href=#window>Window</a></code> object <dfn id=concept-peerconnection-owner title=concept-PeerConnection-owner>has a strong reference</dfn> to
+  any <code><a href=#peerconnection>PeerConnection</a></code> objects created from the constructor
   whose global object is that <code><a href=#window>Window</a></code> object.</p> <!-- we
   could be less strict here, e.g. dropping the reference when there's
   no way for an event to be fired because there's no event handlers
@@ -75747,7 +75758,8 @@
   because no media is streaming; or e.g. dropping the reference when
   the object reaches the CLOSED state. But as dropping the reference
   in those cases is black-box indistinguishable from keeping the
-  reference, I haven't bothered to work out the exact rules. -->
+  reference, I haven't bothered to work out the exact rules. If you do
+  change this, see the /unloading document cleanup steps/. -->
 
 
   <h3 id=event-definitions-0><span class=secno>9.7 </span>Event definitions</h3>

Modified: source
===================================================================
--- source	2011-05-31 22:37:16 UTC (rev 6162)
+++ source	2011-05-31 22:47:19 UTC (rev 6163)
@@ -73442,6 +73442,19 @@
 
    </li>
 
+   <li>
+
+    <p>If the <code>Document</code>'s <code>Window</code> object <span
+    title="concept-PeerConnection-owner">owns</span> any
+    <code>PeerConnection</code> objects whose
+    <span><code>PeerConnection</code> readiness state</span> is not
+    <code title="dom-PeerConnection-CLOSED">CLOSED</code>, then set
+    <code>Document</code>'s <var
+    title="concept-document-salvageable">salvageable</var> state to
+    false.</p>
+
+   </li>
+
    <li><p>If the <code>Document</code>'s <var
    title="concept-document-salvageable">salvageable</var> state is
    false, empty the <code>Document</code>'s <code>Window</code>'s
@@ -86634,8 +86647,9 @@
 
   <h3>Garbage collection</h3>
 
-  <p>A <code>Window</code> object has a strong reference to any
-  <code>PeerConnection</code> objects created from the constructor
+  <p>A <code>Window</code> object <dfn
+  title="concept-PeerConnection-owner">has a strong reference</dfn> to
+  any <code>PeerConnection</code> objects created from the constructor
   whose global object is that <code>Window</code> object.</p> <!-- we
   could be less strict here, e.g. dropping the reference when there's
   no way for an event to be fired because there's no event handlers
@@ -86643,7 +86657,8 @@
   because no media is streaming; or e.g. dropping the reference when
   the object reaches the CLOSED state. But as dropping the reference
   in those cases is black-box indistinguishable from keeping the
-  reference, I haven't bothered to work out the exact rules. -->
+  reference, I haven't bothered to work out the exact rules. If you do
+  change this, see the /unloading document cleanup steps/. -->
 
 
   <h3>Event definitions</h3>




More information about the Commit-Watchers mailing list