Peter, can you take a look? May be related to your recent ArrayBuffer changes.

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

commit 5f79c9231af02dad7125b31af2772bc3f4aa9793
Author: Peter Marshall <petermarshall@chromium.org>
Date: Fri Mar 03 14:42:34 2017

[builtins] Ensure length is within Smi range in TypedArray constructor.

The callsite in ConstructByArrayBuffer could have a length that is
above Smi range if the buffer had such a length. Check this before
calling. Add a test too.

BUG=v8:5977,  chromium:698201 

Change-Id: Ic22046a31607f1f85642c8caf7f5ed064edb3110
Reviewed-on: https://chromium-review.googlesource.com/449813
Commit-Queue: Peter Marshall <petermarshall@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#43589}
[modify] https://crrev.com/5f79c9231af02dad7125b31af2772bc3f4aa9793/src/js/typedarray.js
[modify] https://crrev.com/5f79c9231af02dad7125b31af2772bc3f4aa9793/test/mjsunit/es6/typedarray.js

ClusterFuzz has detected this issue as fixed in range 43588:43589.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5628375382360064

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  raw_length()->IsSmi() || raw_length()->IsUndefined(GetIsolate()) in objects-debu
  
Sanitizer: address (ASAN)

Regressed: V8: 43547:43548
Fixed: V8: 43588:43589

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95Kp-YJw4EgGDqImXNvgAw4FhDTBHcacg0KH_eAO4pLV2_ZmO8QjaHp-JSd2ZTzxlNaXYSj59p3R0xDmejTk_8suHgFKOtusQVC4vWaFZQyEvkXOeLGKZ6OqcBLTwFnaeF8pUrk3sKaYeNhm_VFtbOXfaUePSNiVzEzLoDts0q_FhL_X0fVQlrUPb4NmeLM3vptGWLrnPj-SRZpVQqFR5ctOM-29JxyQ95mC4NltYWOUMCE0RI28Yn10iVR_F5Fzaq99u3KwPeLVuJLO8mYgd-UQZfjkEDSREB6qARXba4DOccJbLw1o3kqgP3cWOVTMDM3KoOw6KfI0Wne_AWEl5uWBceaG8KGQ3BE-kYADPtGUV7HMEQ?testcase_id=5628375382360064


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

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