Stack trace differs. Old validator, hence fullcode, problem?

Most likely due to piping asm.js code through TurboFan without deoptimization support.

ClusterFuzz has detected this issue as fixed in range 45316:45317.

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

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: a44
  
Sanitizer: address (ASAN)

Regressed: V8: 43536:43537
Fixed: V8: 45316:45317

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


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 has detected this issue as fixed in range 46279:46280.

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

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: a44
  
Sanitizer: address (ASAN)

Regressed: V8: 43536:43537
Fixed: V8: 46279:46280

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


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.