Assigning to the concern owner from Find it results --
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 look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Please ignore 'Out of memory' crashes.

ClusterFuzz has detected this issue as fixed in range 443239:443320.

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

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=443239:443320

Minimized Testcase (0.19 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97VMwddh7cq9q2TO7ziXBGAVHFKgRwF49LRvW9vm5B8thRpD0NxE8iD7NOqefKBfoIRQ_cWZmcxFr4EtoZueQzW_60Af-MUvogt6LaeflQ7VppJKZWvLJnQHJC8juPLoS61KFe9zP5_hSCJg2wGHHfxyTx7CDKjg83htijXT6bvLi9QwLqxVX9-gFLzXJdBpEVJVM6murWRhMBCCYs6D0IZwOTBw0J_YTecSNvHX-7Q4itMJzCK7Su9DIjgVh0KNXQWjZKlsrmonUCLeCnEWQtQzmyyN53SdXIYyLvz0NFPV8wVLvVcMhNV7vaIWtfjxJzbAaQQ-2lCvGwVicYFFzA6UKZjgwMppVcB0ES0EgqUCh85p6i8BMeRXl-86pAzu9yYmtj0Dg6upxnJUhEa0Dj7qV6ejw?testcase_id=6485432419483648

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.