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

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:x64,ignition_turbo_opt
  sources: 749
  
Sanitizer: address (ASAN)

Fixed: V8: 43662:43663

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97l6avv1XYF-vfJNe58aeullLUPHnFPsD5oNLfp2y1Va7OmH7BwR8HZbxVLMe3XEy-Efh10w0Iq8YJxA7FieGWb11wXDDjVmKmskqUsWbY8ET4elfzJ6lQ3InorDGFBpz6eD6Qz6jsyrq9eWL4no3-3rav3oxzc1YTvAWHncXRS5ax3p16ERM0bXEsKphgNZWos6MHzphoGCVK-dcJGqdRw-4VbhQjqXzhSGAk4pHTY_QX1fqIo-7q_s23109830SHrejAxm5QNpKUKPP-Y5qvDOpRCBYI8HKOsSDEXg17LTrKStlhPKTOB4Mtm9PXSjuGyV2lgtNIiYl0FsPQTy7n1PpuX4HYl1mnzlLHZa5NRcJAGlnU?testcase_id=4595698445320192


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

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

How did turning on turbofan change semantics of what we compare?

// Wasm issue:
function __f_1(stdlib, foreign, heap) {
  "use asm";
  var __v_2 = new stdlib.Float32Array(heap);
  return {};
}

%OptimizeFunctionOnNextCall(__f_1);
__f_1();

// Output:
# Compared x64,ignition with x64,ignition_turbo
#
# Flags of x64,ignition:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 1234 --ignition --turbo-filter=~ --hydrogen-filter=~ --validate-asm --nocrankshaft
# Flags of x64,ignition_turbo:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 1234 --ignition-staging --turbo --validate-asm
#
# Difference:
+ /usr/local/google/home/machenbach/v8/v8/repro.js:8: TypeError: Cannot read property 'Float32Array' of undefined
#
# Source file:
none
#
### Start of configuration x64,ignition:

### End of configuration x64,ignition
#
### Start of configuration x64,ignition_turbo:
/usr/local/google/home/machenbach/v8/v8/repro.js:8: TypeError: Cannot read property 'Float32Array' of undefined
__f_1();
^



### End of configuration x64,ignition_turbo

This is a asm.js-to-WASM issue. The {AsmJs::IsStdlibValid} checker seems to ignore the unused Float32Array view on the heap. This is not valid according to the JavaScript spec. Even though the {__v_2} variable is not used, it must be initialized and {stdlib.Float32Array} must be checked.

ClusterFuzz has detected this issue as fixed in range 43683:43684.

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:x64,ignition_turbo_opt
  sources: 749
  
Sanitizer: address (ASAN)

Fixed: V8: 43683:43684

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


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.

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