Caused by activating async/await.

ClusterFuzz has detected this issue as fixed in range 36396:36398.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7fffee567e68
Crash State:
  NULL@0x...68
Regressed: V8: r36361:36362
Fixed: V8: r36396:36398

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97CCl2BBlJVo7hU6kuIY6xMl_6VbD_0cPhpWy1JiMISN8qPtGIjaL1xr9D4RSSbLSfkz3s5mqQQVXuVnXSW_GviivJwiTjAxHUCVYg7bQWory_FnzkNSJgqEepyd3KEqzhKMAMG0BekZsr02AhWLuAF1xciTvczV-Wg1Pchx5JAjlXe39s


Additional requirements: Requires Gestures

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.

Dan, is this issue and the other related ones fixed?

ClusterFuzz testcase is verified as fixed, closing issue.

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

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot