// PTAL, simple repro:

Array.prototype[65535] = 0;
function __f_0(x) {
  var __v_0 = new Array();
  __v_0[0] = x;
  return __v_0;
}
__f_0(1);
%OptimizeFunctionOnNextCall(__f_0);
__f_0(1);
Array.prototype.__defineSetter__("0", function() {});
print(__f_0(1));

// This triggers between fullcode and default, but also between ignition and ignition_staging, but not with ignition_turbo.

# Compared x64,fullcode with x64,default
#
# Flags of x64,fullcode:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 1474417455 --nocrankshaft --turbo-filter=~ --novalidate-asm
# Flags of x64,default:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 1474417455
#
# Difference:
- 
+ 1
#
# Source file:
none
#
### Start of configuration x64,fullcode:


### End of configuration x64,fullcode
#
### Start of configuration x64,default:
1

### End of configuration x64,default

This is a Crankshaft issue.

ClusterFuzz has detected this issue as fixed in range 43662:43663.

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

Fuzzer: foozzie_js_mutation
Job Type: foozzie_ignition_staging
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,fullcode:x64,ignition_staging
  sources: 385
  
Sanitizer: address (ASAN)

Regressed: V8: 42370:42371
Fixed: V8: 43662:43663

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv943Dm_8Ecl0A0mvHuX8hxWYAayKwlrAYllU1gtwQ3ilyezNOlJd-8LUwqgmSCs1m1xuArlzQ-tDViFRWVXNJkfTr8qi23hTUivvo3fwp6Uoprp76KfJbNsYCrp2iAZOUy9B3QaDORDvmgZr8xIkEi_96p_OrSLu0KLY-mrid4IYGeKMaAjWhlszNqqKiTrnTJN4e5L4s0u26n5Jv7E9H9TWUz5k5uNGVS196lRbXE1yakS7JxE_Xb9nV5zpZsFlPPFdIjA7nQ9MB5Y40KIRdCqDlhZdYVxQF5waLnCgj-DkXM4ps1oMfnA-r-muoqoHeOMB19Q_HKVmYr6HDV15x18f5Mx01EYrcBL1tB3ehTjDIlrcxJ0?testcase_id=5145881054806016


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

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

We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.