Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

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

commit c0a0c9eb46003204254906df40adcc315d630e28
Author: Andreas Haas <ahaas@chromium.org>
Date: Thu Jul 05 09:54:28 2018

[wasm] Store the wasm interpreter stack on the C++ heap

The stack of the wasm interpreter was stored in a zone. However, when
the stack grows, the previous memory of the stack cannot be reused.
With this CL we allocate the stack on the C++ heap to remove this memory
leak.

R=clemensh@chromium.org

Bug:  chromium:856594 
Change-Id: Idce22c5c1732f7097fc4281c73174892c95f49e2
Reviewed-on: https://chromium-review.googlesource.com/1126301
Commit-Queue: Andreas Haas <ahaas@chromium.org>
Reviewed-by: Clemens Hammacher <clemensh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#54238}
[modify] https://crrev.com/c0a0c9eb46003204254906df40adcc315d630e28/src/wasm/wasm-interpreter.cc

ClusterFuzz has detected this issue as fixed in range 572604:573026.

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

Fuzzer: libFuzzer_v8_wasm_async_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

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

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=525123:525236
Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=572604:573026

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

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.

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

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