Yet another case of ia32 vs. x64 unstable sort problem that somehow kicks in with ishells CL https://chromium-review.googlesource.com/c/548056/:

var __v_3 = 0;
__v_2 = [];
__v_2[200] = undefined;
__v_2[300] = 4;
__v_2[400] = 5;
__v_2[500] = 6;
__v_2[600] = 5;
__v_2[700] = 4;
__v_2[800] = undefined;
__v_2[900] = 3
__v_2[5000] = "filler";
print(__v_2.sort(function(){}));

ClusterFuzz has detected this issue as fixed in range 47306:47307.

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

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

Regressed: V8: 46279:46280
Fixed: V8: 47306:47307

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

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.