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

Issue 815590 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Stack-overflow in blink::InlineFlowBox::PlaceBoxesInBlockDirection

Project Member Reported by ClusterFuzz, Feb 24 2018

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5982999854972928

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffc82085820
Crash State:
  blink::InlineFlowBox::PlaceBoxesInBlockDirection
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=434178:434255

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Feb 24 2018

Labels: OS-Mac
Project Member

Comment 2 by ClusterFuzz, Feb 24 2018

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.
Cc: brajkumar@chromium.org
Labels: M-65 Test-Predator-Wrong CF-NeedsTriage
Unable to find actual suspect through code search and also from the provided CL under regression range, hence adding appropriate label and leaving it as untriaged for further updates.

Thanks!

Comment 4 by e...@chromium.org, Feb 26 2018

Status: WontFix (was: Untriaged)
Stack overflow for deeply nested content => WontFix.
Project Member

Comment 5 by ClusterFuzz, Mar 5 2018

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