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 831461 , hence cc'ing to szager@ and marking it as available.

Thanks!

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0b8a0ab46cd487ecf42081735aef1292abc604b9

commit 0b8a0ab46cd487ecf42081735aef1292abc604b9
Author: Stefan Zager <szager@chromium.org>
Date: Fri Jul 27 22:03:37 2018

Prevent integer overflow when normalizing rect.

BUG= 832498 
R=davidqu@chromium.org

Change-Id: I8325e427df62ed97627ba3090c70b5795a156ba8
Reviewed-on: https://chromium-review.googlesource.com/1153566
Commit-Queue: Emil A Eklund <eae@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578824}
[modify] https://crrev.com/0b8a0ab46cd487ecf42081735aef1292abc604b9/third_party/blink/renderer/core/imagebitmap/image_bitmap.cc

ClusterFuzz has detected this issue as fixed in range 578819:578824.

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

Fuzzer: inferno_twister
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  blink::IntRect::MaxY
  NormalizeRect
  blink::ParseOptions
  
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=578819:578824

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

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

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