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

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/591e3660883178a78d4a9688c0af84483d66848a ([iOS] Adding settings data type into the Google services settings).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

I'm not sure why I received that bug. I'm not part of blink. I work on chrome ios (bling) which doesn't include blink.

With reference to the  Issue 897488 , marking it as won't fix

ClusterFuzz testcase 5782001325703168 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 614361:614362.

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

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

Crash Type: Float-cast-overflow
Crash Address: 
Crash State:
  blink::ScrollbarTheme::ThumbPosition
  blink::Scrollbar::OffsetDidChange
  blink::ScrollableArea::ScrollOffsetChanged
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=581290:581291
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=614361:614362

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

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.