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. 

This is another edge case constant folding bug. Will try to fix them this quarter.

ClusterFuzz has detected this issue as fixed in range 568257:568274.

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

Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  TParseContext::addConstructor
  TParseContext::addFunctionCallOrMethod
  yyparse
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=521502:521564
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=568257:568274

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

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

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