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 not related to your changes.
Thanks.

This is also undefined behavior in the language that we're parsing, so it's of no consequence. We'll look into silencing the sanitizer warning either by making it deterministic or suppressing it.

ClusterFuzz has detected this issue as fixed in range 525156:525174.

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

Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  ppparse
  pp::ExpressionParser::parse
  pp::DirectiveParser::parseExpressionIf
  
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=525156:525174

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

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

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