V8 issue, adding Clusterfuzz Sheriff for more updates on this issue.

I had a look into this one, but it was a Windows ASAN failure in Chrome and Clusterfuzz hadn't bisected it. From the testcase it looked like a pretty involved repro involving scripting of devtools. Not sure what to do with this, so assigning to current Clusterfuzz sheriff so that it is not lost.

ClusterFuzz has detected this issue as fixed in range 561974:561977.

Detailed report: https://clusterfuzz.com/testcase?key=4862179359326208

Fuzzer: ifratric-browserfuzzer-v3
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !CallbackFunction().IsEmpty() in v8_idle_request_callback.cc
  blink::V8IdleRequestCallback::Invoke
  blink::V8IdleRequestCallback::InvokeAndReportException
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=561974:561977

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4862179359326208

See https://github.com/google/clusterfuzz-tools 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 4862179359326208 is verified as fixed, so closing issue as verified.

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