<html>
    <head>
      <base href="https://bugs.webkit.org/" />
    </head>
    <body><span class="vcard"><a class="email" href="mailto:ap&#64;webkit.org" title="Alexey Proskuryakov &lt;ap&#64;webkit.org&gt;"> <span class="fn">Alexey Proskuryakov</span></a>
</span> changed
              <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - REGRESSION: LayoutTest fast/dom/Window/window-properties-performance-resource-timing.html is a flaky failure"
   href="https://bugs.webkit.org/show_bug.cgi?id=166911">bug 166911</a>
        <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">CC</td>
           <td>
               &nbsp;
           </td>
           <td>ggaren&#64;apple.com
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - REGRESSION: LayoutTest fast/dom/Window/window-properties-performance-resource-timing.html is a flaky failure"
   href="https://bugs.webkit.org/show_bug.cgi?id=166911#c3">Comment # 3</a>
              on <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - REGRESSION: LayoutTest fast/dom/Window/window-properties-performance-resource-timing.html is a flaky failure"
   href="https://bugs.webkit.org/show_bug.cgi?id=166911">bug 166911</a>
              from <span class="vcard"><a class="email" href="mailto:ap&#64;webkit.org" title="Alexey Proskuryakov &lt;ap&#64;webkit.org&gt;"> <span class="fn">Alexey Proskuryakov</span></a>
</span></b>
        <pre>The symptom means that window.performance.navigation.__visitedByLogValue__ disappears while the test is running, which would mean that JS wrapper for the object gets collected.

The flakiness dashboard only has results since December 12th, and the test was failing in the same way back then. So, I don't think that we can find out if the test was failing in the same way before concurrent GC (which was enabled on the 11th). It's possible that concurrent GC is simply more effective at quickly collecting the wrapper, and the bug is in the bindings.

I do not know if one needs to do anything custom to protect the GC wrapper these days. Do we still need to add visitAdditionalChildren() functions everywhere?</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>