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

Issue 791192 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
pnangunoori@chromium.org
█ msrchandra@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Stack-overflow in blink::LayoutObject::IsTextOrSVGChild

Project Member Reported by ClusterFuzz, Dec 2 2017 
Detailed report: https://clusterfuzz.com/testcase?key=5017381247385600

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffd0ce8bff8
Crash State:
  blink::LayoutObject::IsTextOrSVGChild
  blink::LayoutObject::ContainingBlock
  blink::LayoutBlock::ComputeBlockPreferredLogicalWidths
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=508795:508862

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Dec 2 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 pnangunoori@chromium.org, Dec 4 2017

Cc: msrchandra@chromium.org pnangunoori@chromium.org
Labels: M-64 Test-Predator-Wrong CF-NeedsTriage
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, Dec 4 2017

Status: WontFix (was: Untriaged)
Project Member

Comment 4 by ClusterFuzz, Dec 11 2017

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