Assigning based on ownership of regressing CL. PTAL?

While crash is distinct, root cause is the same as 793196.

ClusterFuzz has detected this issue as fixed in range 50086:50087.

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

Fuzzer: v8_builtins_generator
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: Heap-buffer-overflow READ 1
Crash Address: 0x0ad0a947
Crash State:
  v8::internal::SliceHelper
  v8::internal::Builtin_ArrayBufferPrototypeSlice
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=49944:49945
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=50086:50087

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

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