Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Unable to find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label

With reference to the  Issue 880040 , CC'ing stevenperron@

Thanks!

ClusterFuzz has detected this issue as fixed in range 606051:606061.

Detailed report: https://clusterfuzz.com/testcase?key=5144476568518656

Fuzzer: libFuzzer_spvtools_opt_legalization_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  get_def_use_mgr()->GetDef(after) && "'after' is not a registered def."
  spvtools::opt::IRContext::ReplaceAllUsesWith
  spvtools::opt::SSARewriter::ApplyReplacements
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=589989:590303
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=606051:606061

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5144476568518656

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.