// PTAL. Typed array max length is arch dependent:

try {
  new Uint8Array(1073741824);
} catch(e) { print(e.message) }

// Output:
# Compared x64,ignition with ia32,ignition
#
# Flags of x64,ignition:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 12334 --ignition --turbo-filter=~ --hydrogen-filter=~ --validate-asm --nocrankshaft
# Flags of ia32,ignition:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 12334 --ignition --turbo-filter=~ --hydrogen-filter=~ --validate-asm --nocrankshaft
#
# Difference:
+ Invalid typed array length
#
# Source file:
none
#
### Start of configuration x64,ignition:

### End of configuration x64,ignition
#
### Start of configuration ia32,ignition:
Invalid typed array length

### End of configuration ia32,ignition

It is indeed MaxSmi, which depends on architecture. Not sure we want to change that.

I'll be mocking this out as part of  issue 688856 .

ClusterFuzz has detected this issue as fixed in range 43051:43052.

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

Fuzzer: foozzie_js_mutation
Job Type: foozzie_ignition_turbo_x64_ia32
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition_turbo:ia32,ignition_turbo
  sources: bed
  
Sanitizer: address (ASAN)

Fixed: V8: 43051:43052

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95OJwI0VTBQ8cMS23xtdmVy3B1lm7I4OhqlAmI0nE2YoUSHRaXXDQAvoDli5pZSdgF5hfzm8pU2APfv-Dov9YoqHZYyX0PbNub5_bTuo2OZOzBZqg84HsCLjc3fddNe8edS2ffrlWQEUJvICsACgVzG2CasBd2bWoMEVSioaxm2_EUAz3qA5A_1I6v7gWTsRR-PxzOQn6SoXVUNif9fdRgxJO8Lzk6OnBFe3i9G3haYaWfLIpgu2BwS6ticJnXswCYHmmSUgr2Tm-i13E2klfrd9Q8CKzLQHEzh10gH8aMuIEyb6nDPoaIHuAuSF1sAfbfl5BsHr12qydKgd6AbMFB5Pcvqib1vfymolMK-HO9IYcw5rgbbJSoPZWA_HlzMptlndd3Uk8AdlbsMTfF11uv4SEUs2A?testcase_id=4777512011038720


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.