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

Issue 761692 link

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



Sign in to add a comment

Stack-overflow in blink::FindPlaceForCounter

Project Member Reported by ClusterFuzz, Sep 4 2017 
Detailed report: https://clusterfuzz.com/testcase?key=4569874335793152

Fuzzer: bj_broddelwerk
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Stack-overflow
Crash Address: 0x7fff581d8ba0
Crash State:
  blink::FindPlaceForCounter
  blink::MakeCounterNodeIfNeeded
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=466203:466217

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

Issue filed automatically.

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

Comment 1 by msrchandra@chromium.org, Sep 4 2017

Cc: msrchandra@chromium.org
Labels: M-63 Test-Predator-Wrong
Owner: yutak@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using Code Search for the file, "LayoutCounter.cpp" assigning to concern owner who might be related.

@yutak -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Comment 2 by yutak@chromium.org, Sep 4 2017

Components: Blink>Layout
Owner: ----
Status: Untriaged (was: Assigned)
Wait for layout team to re-triage.

Comment 3 by msrchandra@chromium.org, Sep 4 2017

Labels: CF-NeedsTriage
@yutak -- Thank you for the update.

Comment 4 by e...@chromium.org, Sep 6 2017

Status: WontFix (was: Untriaged)
Stack overflows for deeply nested DOMs are considered WontFix.
Project Member

Comment 5 by ClusterFuzz, Sep 14 2017

Labels: Needs-Feedback
ClusterFuzz testcase 4569874335793152 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 6 by ClusterFuzz, Sep 17 2017

Labels: OS-Linux
►

Sign in to add a comment