Hey Jaro, can you have a look?

This is an out-of-memory situation. It does not reproduce on my box with the same stack trace.

ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5335767187980288

Fuzzer: jsbell_serviceworker
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  old_gen_size > 0 in heap.cc
  v8::internal::Heap::CollectGarbage
  v8::internal::Heap::HandleGCRequest
  v8::internal::Invoke
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=windows_asan_chrome_no_sandbox&range=379564:379959

Minimized Testcase (0.19 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv96G6UMu5NNge7qnc34CY3m7E_8ArlslU6JS7pkJX2DTyFqBIAdQ1_HeefVZv_7yn-B5hn-8B8RFVmqeoa1taASagTrZeE6tQ9uyJJubAS9cfllkdS2ranhztREpjwmP8lU3WHW47jfPjStZB9fiklINLr_egQ
<script>
(function(instance) {
    (function() {
    }());
    var result = instance.register("", {scope: Array(66211047)});
  window.location.reload();
}(navigator.serviceWorker));
</script>


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase is verified as fixed, closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot