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 assigning owner based on suspected regression changelist https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools/+/dd4157dcee70479240f0623d015fde0b6c86e1eb (Sink (#2284)).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Fixed with https://github.com/KhronosGroup/SPIRV-Tools/pull/2308.

ClusterFuzz has detected this issue as fixed in range 624608:624632.

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

Fuzzer: libFuzzer_spvtools_opt_performance_fuzzer
Fuzz target binary: spvtools_opt_performance_fuzzer
Job Type: windows_libfuzzer_chrome_asan
Platform Id: windows

Crash Type: Null-dereference READ
Crash Address: 0x000000000008
Crash State:
  std::_Func_impl_no_alloc<`lambda
  std::_Func_impl_no_alloc<`lambda
  spvtools::opt::analysis::DefUseManager::WhileEachUse
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=623888:623921
Fixed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=624608:624632

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for instructions to reproduce this bug locally.

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

ClusterFuzz testcase 6540120513314816 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.