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

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

I'm guessing this is WontFix? We had a similar one in the validator.

ClusterFuzz has detected this issue as fixed in range 595871:595872.

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

Fuzzer: libFuzzer_spvtools_opt_performance_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  def && "Definition is not registered."
  spvtools::opt::analysis::DefUseManager::AnalyzeInstUse
  spvtools::opt::analysis::DefUseManager::AnalyzeInstDefUse
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=579911:580305
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=595871:595872

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

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.