Mine.

Umm, this is the async arrow functions stuff again, which I just fixed. And the test is exactly the one I added when fixing it:

https://chromium-review.googlesource.com/c/v8/v8/+/674695

ClusterFuzz has detected this issue as fixed in range 503967:504091.

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

Fuzzer: mbarbella_js_mutation
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  scope_data->length() > index_ in preparsed-scope-data.cc
  v8::platform::PrintStackTrace
  v8::internal::ConsumedPreParsedScopeData::RestoreData
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=499408:499633
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=503967:504091

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

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.

This bug has been closed for more than 14 weeks. Removing security view restrictions.

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