Integer-overflow in blink::IntRect::UniteEvenIfEmpty |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4824312327176192 Fuzzer: ifratric-browserfuzzer-v3 Job Type: linux_ubsan_chrome Platform Id: linux Crash Type: Integer-overflow Crash Address: Crash State: blink::IntRect::UniteEvenIfEmpty blink::LayoutObject::AbsoluteBoundingBoxRect blink::ScrollingCoordinator::ComputeShouldHandleScrollGestureOnMainThreadRegion Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=549059:549062 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4824312327176192 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Apr 11 2018
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.
,
Apr 11 2018
,
Apr 12 2018
We generally don't care about integer overflows from CSS values.
,
Apr 19 2018
ClusterFuzz testcase 4824312327176192 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. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ClusterFuzz
, Apr 11 2018Labels: Test-Predator-Auto-Components