Caused by activating async/await.

I can reproduce this locally, and Caitlin's patch at https://codereview.chromium.org/1992093003 prevents the issue from occurring.

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

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_dbg
Platform Id: linux

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

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94Kzv3LLUnXZVRfw4nVX6w7FyQYvLVKUtDtIOiBE4M78chc7s_KE1Ph1CEv5YFQekCE4dWAvaD7AvuNRJ2wFS28_-XjmmsY9qwEf9SnnhknJr8UydtAW9RSMOXBGBCBh7wkr1e16Hn10V3bgTSW8cSWnwW6AMZXpx8OVaAJuoK302ejueo


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.

Marking Fixed per #2 (that CL has landed) and #3.

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