Maybe the same as  Issue 761654  ?

I'm assuming dup, and it sounds like it can't yet be reverified in CF.

ClusterFuzz has detected this issue as fixed in range 499408:499633.

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

Fuzzer: v8_builtins_generator
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  len->ToUint32(&int_l) in builtins-typedarray.cc
  v8::platform::PrintStackTrace
  v8::internal::Builtin_Impl_TypedArrayPrototypeSet
  
Sanitizer: address (ASAN)

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

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

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