Assigning to the concern owner from Find it --

The result is a list of CLs that change the crashed files. 

Author: titzer
Project: chromium-v8
Changelist: https://chromium.googlesource.com/v8/v8.git/+/3f207617d7141cfc3a7051a243f8bbfb98c879c7
Time: Wed Oct 26 16:56:05 2016
Lines 1595-1605 of file wasm-interpreter.cc which potentially caused crash are changed in this cl (frame #2, "v8::internal::wasm::ThreadImpl::Execute").
Minimum distance from crash line to modified line: 0. (file: wasm-interpreter.cc, crashed on: 1595, modified: 1595).

@titzer -- Could you please take a look into the issue, kindly reassign if it is not related your changes.

ClusterFuzz has detected this issue as fixed in range 442270:442327.

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

Fuzzer: libfuzzer_v8_wasm_code_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  v8_wasm_code_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=427848:428120
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan&range=442270:442327

Minimized Testcase (0.04 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96S5K5pLmCTDOmqrTVm8F-NtzSoar0XTAwrjJh8SPplDpMnRQz8Ov2RXW707zIB0wlr2PWOmcG5eUDDJuMmFmlae896ipUerlM23gVDZkLy7Ed_ZPO8WBja1Ie8011WP2AmvFBjn86Ai9RSmDu7YghnzZJ2CQ?testcase_id=5268762833190912

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.

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

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