New issue
Advanced search Search tips

Issue 788458 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
kkaluri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Stack-overflow in blink::LayoutBoxModelObject::ComputedCSSPadding

Project Member Reported by ClusterFuzz, Nov 24 2017 
Detailed report: https://clusterfuzz.com/testcase?key=6006239082577920

Fuzzer: attekett_dom_fuzzer
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Stack-overflow
Crash Address: 0x7fff52190fe0
Crash State:
  blink::LayoutBoxModelObject::ComputedCSSPadding
  blink::LayoutBox::ContentLogicalWidth
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=463171:463172

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Nov 24 2017

Components: Blink>Layout
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 kkaluri@chromium.org, Nov 27 2017

Cc: kkaluri@chromium.org
Labels: M-63 CF-NeedsTriage Test-Predator-Wrong
Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.

Thank You...

Comment 3 by e...@chromium.org, Nov 30 2017

Status: WontFix (was: Untriaged)
Project Member

Comment 4 by ClusterFuzz, Dec 7 2017

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