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=4673663957991424

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_dbg
Platform Id: linux

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

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv970asEFbgdc08JrOCUKH29GM7FoEKwoVrQOxRYPoIhWxb4WS4ETkktuz3_Azr_uugb1ugbNpyE7wMLu4_6jNKpHnlSL1bTjdqWu0wokAZobf3iTFxWVfClb4IbVi24GCXrKC2gnYfbJij5bClboewN5TNSC-I2jWk2vRd_Zj1wJgaxkDDY


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 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