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

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

@capn -- Could you please look into this issue. 
Assigning this issue to you, as per the update we received from you in the  Issue 781505 . Please reassign if it is not related to your changes.
Thanks. 

Totally benign. The assert just warns us of a loop iteration count determination that we're not handling specifically, so we treat it as a loop with high iteration count (which is always a safe fallback).

ClusterFuzz has detected this issue as fixed in range 562444:562449.

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

Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  false
  glsl::OutputASM::loopCount
  glsl::OutputASM::visitLoop
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=521495:521545
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=562444:562449

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

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 5782772252934144 is verified as fixed, so closing issue as verified.

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