New issue
Advanced search Search tips

Issue 843258 link

Starred by 1 user
Status: WontFix
Owner:
chrishtr@chromium.org
Closed: May 2018
Cc:
pnangunoori@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Stack-overflow in blink::LayoutObject::FindNextLayer

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

Fuzzer: inferno_layout_test_unmodified
Job Type: mac_asan_content_shell
Platform Id: mac

Crash Type: Stack-overflow
Crash Address: 0x7fff509acf80
Crash State:
  blink::LayoutObject::FindNextLayer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=546091:546111

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, May 15 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.

Comment 2 by pnangunoori@chromium.org, May 16 2018

Cc: pnangunoori@chromium.org
Labels: M-67 Test-Predator-Wrong
Owner: chrishtr@chromium.org
Status: Assigned (was: Untriaged)
As per the  Issue 837971  owner, assigning this issue to @chrishtr.
@chrishtr-- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thanks.

Comment 3 by e...@chromium.org, May 16 2018

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

Comment 4 by ClusterFuzz, May 23 2018

Labels: OS-Linux
Project Member

Comment 5 by ClusterFuzz, May 24 2018

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