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/+/07b115f854d6fe6e0a05c0d9e7143cb9580dfe28
Time: Mon Jun 12 11:59:14 2017
Lines 107, 403, 966-973 of file module-decoder.cc which potentially caused crash are changed in this cl (frame #3, "v8::internal::wasm::"; frame #4, "consume_string"; frame #5, "DecodeImportSection").
Minimum distance from crash line to modified line: 0. (file: module-decoder.cc, crashed on: 403, modified: 403).

@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/539402

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

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

Fuzzer: libFuzzer_v8_wasm_imports_section_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  offset_ <= offset_ + length_ in wasm-module.h
  WireBytesRef
  v8::internal::wasm::consume_string
  
Sanitizer: address (ASAN)

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

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


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.