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

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

Looks like this might be related to the Swiftshader roll in crrev.com/c/806725, sugoi can you take a look? Thanks.

ClusterFuzz has detected this issue as fixed in range 550284:550296.

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

Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  TParseContext::nonInitErrorCheck
  TParseContext::parseSingleDeclaration
  yyparse
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=521502:521555
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=550284:550296

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

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

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot