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.
Could someone please look into the issue.
Thank You.

+xidachen@ since he is the owner of more Float-cast-overflow clusterfuzz issues.
xidachen@ could you please take a look?

bokan@: could you triage this? As far as I know, this is something being turned on by cluter fuzz recently.

ClusterFuzz testcase 4904636654551040 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

ClusterFuzz has detected this issue as fixed in range 570347:570348.

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

Fuzzer: inferno_twister
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Float-cast-overflow
Crash Address: 
Crash State:
  blink::Element::ScrollLayoutBoxBy
  blink::Element::scrollBy
  scrollBy2Method
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=552707:552711
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=570347:570348

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

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.