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 provide possible suspect using Predator, CL and Code Search.

sugoi@ -- Could you please look into this issue as the crash data from the test case of the  Issue 823031  seems to be similar to the issue.

Thanks!

The issue is an integer overflow in blink. Nothing to do with SwiftShader.
Assigning to eae@, who's the last person to have touched code in that area, so he can assign it to the proper person.

ClusterFuzz has detected this issue as fixed in range 567089:567097.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  blink::LayoutFrameSet::UpdateLayout
  blink::LayoutBlockFlow::PositionAndLayoutOnceIfNeeded
  blink::LayoutBlockFlow::LayoutBlockChild
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=523880:523906
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=567089:567097

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

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.