ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_v8_mipsel_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  edge.to() == NodeProperties::GetControlInput(use) in src/compiler/scheduler.cc
  
Regressed: V8: r34586:34587

Minimized Testcase (0.25 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv96VOip5RM6DROFZz7Ah-GNbE1VCSUu0AKC1WaR_DLhOGLnqgn4w_j16U99-xaXJcX6hJ6kzzRq6MvUp5-vzGKHR9JhMI_l2Ot0VUmNgrif1VvoqxEvdt_jgtB67hYfEbaNJ9T_eedzBNp1c3Cv62NkPQtyPYw
  function __f_6(){
    'use asm';
    function __f_8() {
      var __v_16 = 1, __v_15 = 0, __v_17 = 0;
      do {
__v_15 | 0 % 2 | 0;
      } while(0);
    }
    return { __f_8: __f_8 };
  }
  var __v_14 = Wasm.instantiateModuleFromAsm(__f_6.toString());


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.

This was due to the scheduler inspecting uses from dead (floating) phis.

I disabled the assertion (which is safe) until the scheduler is taught to stop looking at dead code.

 Issue 599070  has been merged into this 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