Assigning to the concern owner using Predator results --
The result is a list of CLs that change the crashed files. 

Author: Clemens Hammacher
Project: chromium-v8
Changelist: https://chromium.googlesource.com/v8/v8.git/+/6a36b2a040eed8fc934753d463af41f14b48e356
Time: Fri Jun 09 18:37:54 2017
Lines 39-40 of file wasm.cc which potentially caused crash are changed in this cl (frame #4, "LLVMFuzzerTestOneInput"). 

Lines 84-104 of file wasm-module-runner.cc which potentially caused crash are changed in this cl (frame #3, "v8::internal::wasm::testing::CompileAndRunWasmModule").
Minimum distance from crash line to modified line: 0. (file: wasm-module-runner.cc, crashed on: 84, modified: 84).

@clemensh -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

https://chromium-review.googlesource.com/539401

ClusterFuzz has detected this issue as fixed in range 481047:481113.

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

Fuzzer: libFuzzer_v8_wasm_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  thrower->error() == instance.is_null() in wasm-module.cc
  v8::internal::wasm::SyncCompileAndInstantiate
  v8::internal::wasm::testing::CompileAndRunWasmModule
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=478667:478736
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=481047:481113

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


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.