Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.

Thank You...

I am quite busy currently, otherwise I would check this myself.
Andreas, could you take a look?

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

commit bfbaefd863d8fc0a748fe1a010692d351a94f163
Author: Andreas Haas <ahaas@chromium.org>
Date: Tue Jul 31 11:08:46 2018

[wasm] Add estimate size for the WasmInterpreter

The lifetime of the WasmInterpreter is managed by the GC. However, we
did not tell the GC the amount of memory consumed by the interpreter.
Therefore it was possible to fill up memory with instances of the
interpreter without triggering a GC to free memory. With this CL we pass
the size of the stack as an estimate for the size of the interpreter. At
least in the fuzzer the stack is the dominating factor for memory
consumption.

R=clemensh@chromium.org

Bug:  chromium:863198 
Change-Id: Ic5cb0bd364500bcff793a1fd53d2d0113196dfe2
Reviewed-on: https://chromium-review.googlesource.com/1156385
Reviewed-by: Clemens Hammacher <clemensh@chromium.org>
Commit-Queue: Andreas Haas <ahaas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#54810}
[modify] https://crrev.com/bfbaefd863d8fc0a748fe1a010692d351a94f163/src/wasm/wasm-debug.cc

ClusterFuzz has detected this issue as fixed in range 579426:579434.

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

Fuzzer: libFuzzer_v8_wasm_async_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  v8_wasm_async_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=500406:500452
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=579426:579434

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

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

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