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

Issue 841440 link

Starred by 1 user
Status: WontFix
Owner:
schenney@chromium.org
Closed: May 2018
Cc:
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Integer-overflow in blink::IntRect::UniteEvenIfEmpty

Project Member Reported by ClusterFuzz, May 9 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5976696495538176

Fuzzer: inferno_twister
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  blink::IntRect::UniteEvenIfEmpty
  blink::CompositingRequirementsUpdater::OverlapMap::FinishCurrentOverlapTestingCo
  blink::CompositingRequirementsUpdater::Update
  
Sanitizer: undefined (UBSAN)

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

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, May 9 2018

Components: Platform
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

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

Comment 2 by brajkumar@chromium.org, May 10 2018

Cc: brajkumar@chromium.org
Labels: M-67 Test-Predator-Wrong
Owner: schenney@chromium.org
Status: Assigned (was: Untriaged)
This issue looks similar to  bug 837300 , hence assigning to schenney@ for more updates on it.

schenney@ Could you please take a look in to it? 

Thanks!

Comment 3 by schenney@chromium.org, May 10 2018

Labels: ClusterFuzz-Ignore
Status: WontFix (was: Assigned)
This is code that needs to be highly efficient and overflow is not a problem.
Project Member

Comment 4 by ClusterFuzz, May 17 2018

Labels: Needs-Feedback
ClusterFuzz testcase 5976696495538176 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.
Project Member

Comment 5 by ClusterFuzz, Jul 3

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 5976696495538176 appears to be flaky, updating reproducibility label.
►

Sign in to add a comment