Regression range points to 3cfacadec1013c016ae76c7766f397a0b2382e47, requires "--wasm-interpret-all" to reproduce.

Lowering priority, as it requires '--wasm-interpret-all'. Also, no security implications.

Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Increasing priority, since this will also fail if the interpreter is used for debugging.

CL: https://crrev.com/c/735354

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

commit 68a087f81132b5c26ba3a6468b95bea4389fc0f6
Author: Clemens Hammacher <clemensh@chromium.org>
Date: Wed Oct 25 09:59:14 2017

[wasm] [interpreter] Handle ToNumber failure on imports

We were already handling the case that a called import throws, but if
it returned an error which is not convertible to a number, we failed
with a CHECK error.
This CL fixes this.

R=titzer@chromium.org

Bug:  chromium:771970 
Change-Id: I6c9983459109d49c43304610b696d49de986a250
Reviewed-on: https://chromium-review.googlesource.com/735354
Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
Reviewed-by: Ben Titzer <titzer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#48912}
[modify] https://crrev.com/68a087f81132b5c26ba3a6468b95bea4389fc0f6/src/wasm/wasm-interpreter.cc
[modify] https://crrev.com/68a087f81132b5c26ba3a6468b95bea4389fc0f6/test/mjsunit/wasm/interpreter.js

ClusterFuzz has detected this issue as fixed in range 48911:48912.

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

Fuzzer: ochang_js_fuzzer
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  (location_) != nullptr in handles.h
  Check
  ToHandleChecked
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=44184:44185
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48911:48912

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

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.

ClusterFuzz testcase 4903431646216192 is verified as fixed, so closing issue as verified.

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