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

commit 9f5593b8434007792840e953805aca3527f917ee
Author: Michael Starzinger <mstarzinger@chromium.org>
Date: Wed Jul 12 14:31:44 2017

[compiler] Leave stack space for job finalization.

This makes sure we leave some gap on the stack whenever compilation jobs
are being finalized. Such a finalization can trigger assembling back on
the main thread, hence requiring a non-negligible amount of stack. This
is in sync with other {Runtime_CompileFoo} methods.

R=ishell@chromium.org
BUG= chromium:740400 , chromium:741599 

Change-Id: I96fbd524c3cd443a1f5a8e22925b92407fadfb63
Reviewed-on: https://chromium-review.googlesource.com/568142
Reviewed-by: Igor Sheludko <ishell@chromium.org>
Commit-Queue: Michael Starzinger <mstarzinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#46595}
[modify] https://crrev.com/9f5593b8434007792840e953805aca3527f917ee/src/runtime/runtime-compiler.cc

ClusterFuzz has detected this issue as fixed in range 485940:486007.

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

Fuzzer: inferno_js_fuzzer
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: Stack-overflow
Crash Address: 0x077e2000
Crash State:
  v8::internal::JSArray::AnythingToArrayLength
  v8::internal::Accessors::ArrayLengthSetter
  v8::internal::PropertyCallbackArguments::Call
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=342718:342907
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=485940:486007

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 6716709783470080 is verified as fixed, so closing issue.

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