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

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

Since it is related to Swiftshader component, assigning it to capn@

capn@ could you please look into it


Thank You...

The integer overflow is also undefined behavior in the GLSL language that this is compiling, so it's benign.

Casting to unsigned and then back to signed would silence UBSAN since unsigned overflow is well defined.

ClusterFuzz has detected this issue as fixed in range 529109:529114.

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

Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  ConstantUnion::operator+
  TIntermConstantUnion::fold
  TIntermediate::addBinaryMath
  
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=529109:529114

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

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

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