This is mine, I take it. :)

This is a function table size overflow:

function Module() {
  "use asm";
  function f() {
    undeclared[1 & 1073741823]();
  }
}
var m = Module();

 Issue 719333  has been merged into this issue.

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

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

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_asm
  sources: 177
  
Sanitizer: address (ASAN)

Regressed: V8: 44685:44686
Fixed: V8: 45316:45317

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


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

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

Nope, still an issues.

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/a621462bab818eedf079c6e0aeadb981b3c4c746

commit a621462bab818eedf079c6e0aeadb981b3c4c746
Author: Michael Starzinger <mstarzinger@chromium.org>
Date: Fri May 19 14:14:17 2017

[asm.js] Fix excessive function table sizes.

This fixes crashes during validation when trying to construct modules
with excessively large function tables. The {WasmModuleBuilder} now
gracefully checks against existing WebAssembly implementation limits.

R=clemensh@chromium.org
TEST=mjsunit/regress/regress-crbug-715455
BUG= chromium:715455 

Change-Id: Ia9738cb0b49a1eb4caf073b75301c0303f295699
Reviewed-on: https://chromium-review.googlesource.com/509530
Commit-Queue: Michael Starzinger <mstarzinger@chromium.org>
Reviewed-by: Clemens Hammacher <clemensh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#45429}
[modify] https://crrev.com/a621462bab818eedf079c6e0aeadb981b3c4c746/src/asmjs/asm-parser.cc
[modify] https://crrev.com/a621462bab818eedf079c6e0aeadb981b3c4c746/src/asmjs/asm-parser.h
[modify] https://crrev.com/a621462bab818eedf079c6e0aeadb981b3c4c746/src/wasm/wasm-module-builder.cc
[add] https://crrev.com/a621462bab818eedf079c6e0aeadb981b3c4c746/test/mjsunit/regress/regress-crbug-715455.js

ClusterFuzz has detected this issue as fixed in range 45428:45429.

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

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_asm
  sources: 177
  
Sanitizer: address (ASAN)

Regressed: V8: 44685:44686
Fixed: V8: 45428:45429

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


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.

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