Async/await vs Ignition generators issue.

ClusterFuzz has detected this issue as fixed in range 36937:36938.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_ignition_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  OperandsAreValid(bytecode, 1, operand0) in bytecode-array-builder.cc
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_d8_ignition_dbg&range=36638:36639
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_d8_ignition_dbg&range=36937:36938

Minimized Testcase (0.07 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv95AZfjVI_jHeVyeJGUDt8JHQYPWT3Q20-irHJHpGrzkylgf3JSxZ2UgrwIt9goONTJSWQW-WcN9C8Gn0EVk4lviztxPrPSGXIEVXws5nmlm1R7NjOjX12AdHgzhJw-ZNrpwKHwPdEB5wXG_2-gR7sjPpSB5YA
async function __f_3() {
       await
             __f_2();
}
__f_3();


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.

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