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

commit cc1249b779fae9fbd019f6c6861bf1d1534f0a8c
Author: mstarzinger <mstarzinger@chromium.org>
Date: Mon Sep 05 23:02:55 2016

[compiler] Bytecode preparation fails for asm.js modules.

This handles the case where preparation of bytecode might fail inside
Compiler::EnsureBytecode due to the underlying function being a fully
validated asm.js module. We simply bailout of bytecode preparation.

R=bradnelson@chromium.org
TEST=mjsunit/regress/regress-crbug-644111
BUG= chromium:644111 

Review-Url: https://codereview.chromium.org/2309853002
Cr-Commit-Position: refs/heads/master@{#39187}

[modify] https://crrev.com/cc1249b779fae9fbd019f6c6861bf1d1534f0a8c/src/compiler.cc
[add] https://crrev.com/cc1249b779fae9fbd019f6c6861bf1d1534f0a8c/test/mjsunit/regress/regress-crbug-644111.js

ClusterFuzz has detected this issue as fixed in range 39172:39192.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_v8_d8_tot
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  info->shared_info()->HasBytecodeArray() in compiler.cc
  
Regressed: V8: r38036:38051
Fixed: V8: r39172:39192

Minimized Testcase (0.14 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv95TIIgeFQDf8-bWHM52DUmoB4xzNifSFa0XqHO3SVHsj1AmKctW-Et6xfDuFH9KT5rdyJ7hvtRH8k2F05Zu8v85rbIFQAANnxrVPO41jgAbbTuE-rJt_-piqzA85bfKZsZLdd2tIaW3B04w3BZfJwqLE6vfvA?testcase_id=4752662237282304
function __f_0() {
  "use asm";
  function __f_1(i4, i5) {
    i4 = i4 | 0;
    i5 = i5 | 0;
  }
  return {'__f_1': __f_1}
}
  var __v_0 = __f_0();


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.

This is done.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot