Calling {indexOf} on a typed array without arguments is borked. Introduced in b2efe57cdfb87698599c1135581b258ab6fd8aa5. Can't set non project members as owners in the issue tracker, hence setting cbruni@ as owner instead.

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/af63679d0531992f70ed96db58b72b1b3449aa48

commit af63679d0531992f70ed96db58b72b1b3449aa48
Author: cwhan.tunz <cwhan.tunz@gmail.com>
Date: Tue Mar 14 16:26:24 2017

Set undefined when calling %TypedArray%.indexOf without arguments

Set undefined to the first argument (search element) if the first
argument is not given in %TypedArray%.prototype.indexOf or
%TypedArray%.prototype.includes

BUG= chromium:700894 

Review-Url: https://codereview.chromium.org/2748113002
Cr-Commit-Position: refs/heads/master@{#43794}

[modify] https://crrev.com/af63679d0531992f70ed96db58b72b1b3449aa48/src/builtins/builtins-typedarray.cc

ClusterFuzz has detected this issue as fixed in range 43793:43794.

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

Fuzzer: v8_builtins_generator
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  index < length() in builtins-utils.h
  
Sanitizer: address (ASAN)

Regressed: V8: 43740:43741
Fixed: V8: 43793:43794

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94muEtc-R7D63s1RXx8ZtVF0Nz7naoVHakATk5aWgoFZDeFd6ezzaOQ-yrzdGuR68hfLRHTKM3N6BrDOGId7OxlhzPxCFTnMoa0hbNH82w2QRRraogOFdiH_HK31YGyW5DTnoKDCh9ucwXLxao0F9R-BwgQv4tvr5SslE4I_IGGYls0QY61-UKfGdLbiH75AhJ4IWkzS4j3AFuZqShAhhB8bmSkOqvWEvz1b9rKfCwFgXg6FHlsd3oTTdyg7h6e63BjPBG7PH45oO-ecP38oPShtJkBn3wyYMaspN2OhVmpX7TjL8GOw4GxVmYcuC19ojhTU6mN7qNXtGAH1AukMYFhXCk2e4fqXIaRdLmcErBV5mRL1N4?testcase_id=5136766001741824


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 5136766001741824 is verified as fixed, so closing issue.

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