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/+/238613f2364a704efa82a4e252f6c2058d7b1924 (Fix build on case-sensitive file systems after the Great Blink mv.).

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.

This issue looks similar to  bug 830470 , hence assigning to the same dev for more updates on this issue.

szager@ Could you please take a look in to this issue?

Thanks!

ClusterFuzz has detected this issue as fixed in range 552255:552256.

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

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

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  blink::IntPoint::Move
  blink::operator+=
  blink::EmbeddedContentPainter::PaintContents
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=549059:549062
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=552255:552256

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

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.

ClusterFuzz testcase 5785999259729920 is verified as fixed, so closing issue as verified.

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