Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/3b64764b1d7ea62a5ddda301cdcb5547186754c5 (Make JSTypedArray::length() and length_value() ignore neutering.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Issue 904765 has been merged into this issue.

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

commit 04af85c6a9fabd7b026d10aedbeb5fa24dcfb1d8
Author: Georg Neis <neis@chromium.org>
Date: Tue Nov 13 11:47:00 2018

[typed-array] Fix CopyElements.

An oversight in my previous change (3b64764b1d7ea) could
cause a CHECK failure.

Bug:  chromium:904707 
Change-Id: Ie5f1c500bddc00741b889f78ae9ecd9af581ba5c
Reviewed-on: https://chromium-review.googlesource.com/c/1333409
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Georg Neis <neis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#57459}
[modify] https://crrev.com/04af85c6a9fabd7b026d10aedbeb5fa24dcfb1d8/src/elements.cc
[add] https://crrev.com/04af85c6a9fabd7b026d10aedbeb5fa24dcfb1d8/test/mjsunit/regress/regress-904707.js

ClusterFuzz has detected this issue as fixed in range 57458:57459.

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

Fuzzer: ochang_js_fuzzer
Job Type: linux_ubsan_vptr_d8
Platform Id: linux

Crash Type: Ill
Crash Address: 0x562c9fa3909e
Crash State:
  v8::internal::TypedElementsAccessor<
  CopyElementsHandleImpl
  v8::internal::ElementsAccessorBase<v8::internal::TypedElementsAccessor<
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=56432:56433
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=57458:57459

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

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

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