ClusterFuzz has detected this issue as fixed in range 36972:36993.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_v8_d8_tot
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  Node::New() Error: #NUMBER:DeoptimizeUnless[1] is nullptr in node.cc
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_v8_d8_tot&range=36944:36972
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_v8_d8_tot&range=36972:36993

Minimized Testcase (2.70 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94Y9VMeHTGzgypcWKW9bfqgxOhs9Yvp6bCntxQxp6ctAh-LtFJLHdgISnmFRAKOuuEFVS46Dt5P3aCaRib96sru3tRebRoI2XbsH-1Tf7WxhghwjinGx2u-KSBoJ8xNfswg5jdR3v87F4ohoOy4Frbo7Vbftg

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