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

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

Unable to find actual suspect through code search and also from the provided CL, hence marking it as untriaged.

capn@ Could you please take a look in to this issue?

Thanks!

gpu triage: ping on idle p1 bug.

This is just a GPU process crash for a fabricated edge case, so it's not very high priority. We'll also replace the GLSL compiler with glslang at some point, so it's probably not worth spending time on this.

ClusterFuzz has detected this issue as fixed in range 567530:567542.

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

Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  TParseContext::addFunctionCallOrMethod
  yyparse
  PaParseStrings
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=521492:521536
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=567530:567542

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

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.

Possibly got fixed by https://swiftshader-review.googlesource.com/19308

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

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