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

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

Assigning to SwiftShader team for more updates.

@capn - Could you please look into this issue?

Thanks! 

This might be related to a tracking bug: https://bugs.chromium.org/p/swiftshader/issues/detail?id=85

ClusterFuzz has detected this issue as fixed in range 562443:562447.

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

Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  glsl::OutputASM::loopCount
  glsl::OutputASM::visitLoop
  TIntermLoop::traverse
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=529739:529747
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=562443:562447

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

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.

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

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

Affected by https://swiftshader-review.googlesource.com/18988, but I'm not sure if that actually fixed it or just moved the issue.