New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 760029 link

Starred by 1 user
Status: WontFix
Owner:
chrishtr@chromium.org
Closed: Sep 2017
Cc:
ifratric@google.com
█ msrchandra@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Integer-overflow in CornerStart

Project Member Reported by ClusterFuzz, Aug 29 2017 
Detailed report: https://clusterfuzz.com/testcase?key=4650788455710720

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

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  CornerStart
  blink::CornerRect
  blink::PaintLayerScrollableArea::ResizerCornerRect
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=370022:370027

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.

Comment 1 by msrchandra@chromium.org, Aug 29 2017

Cc: msrchandra@chromium.org
Components: Blink>Scroll
Labels: M-62 Test-Predator-Wrong
Owner: chrishtr@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using Code Search for the file, "PaintLayerScrollableArea.cpp" assigning to the concern owner.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/2ffc647aa11247778397a240e7c90426f58c7edc

@chrishtr -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Comment 2 by chrishtr@chromium.org, Sep 11 2017

Status: WontFix (was: Assigned)
Project Member

Comment 3 by ClusterFuzz, Sep 19 2017

Labels: Needs-Feedback
ClusterFuzz testcase 4650788455710720 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