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

Issue 743689 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Stack-overflow in blink::ShapeCache::AddSlowCase

Project Member Reported by ClusterFuzz, Jul 15 2017

Issue description

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_chrome_mp
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7fffb43b0dc0
Crash State:
  blink::ShapeCache::AddSlowCase
  blink::CachingWordShapeIterator::ShapeWordWithoutSpacing
  blink::CachingWordShapeIterator::ShapeWord
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=144946:145047

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


Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Labels: Pri-2
Stack-overflow, Out of memory and Timeout issues are 'P2'.
Project Member

Comment 2 by ClusterFuzz, Aug 26 2017

Labels: OS-Mac
Cc: msrchandra@chromium.org adenilso...@arm.com e...@chromium.org pnangunoori@chromium.org
Labels: M-63 Test-Predator-Wrong-CLs
Predator and CL could not provide any possible suspects.
Using the code search for the file, “ShapeCache.h” cc'ing the concern owner from GIT blame.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/498c6180fb8e7993176e089ac9225f0357d1a21a

@adenilson.cavalcanti -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

Thank You.
Cc: -e...@chromium.org
Owner: e...@chromium.org
Status: Assigned (was: Untriaged)
Assigning to review owner as the concern owner is not a chromium owner.
Thank You.

Comment 5 by e...@chromium.org, Sep 15 2017

Status: WontFix (was: Assigned)
Stack overflows due to deeply nested DOM structures are considered WontFix.
Project Member

Comment 6 by ClusterFuzz, Sep 23 2017

Labels: Needs-Feedback
ClusterFuzz testcase 6222186007494656 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.
It is a bit weird as we are neither making recursive calls or allocating memory in this change (actually the code would construct temporary hasher objects before the change).

What you think Emil?
Cc: cavalcantii@chromium.org

Comment 9 by e...@chromium.org, Sep 24 2017

The test case uses the DOM mutation API to recursively wrap an element leading to a very deep DOM structure.

Clusterfuzz returns ~10 variations of this a week and by design they will all cause a stack overflow.
That is quite interesting, thanks for the explanation.

 Issue 768123  has been merged into this issue.
Cc: kkaluri@chromium.org
 Issue 773226  has been merged into this issue.
Project Member

Comment 13 by ClusterFuzz, Oct 10 2017

Components: Platform
Labels: Test-Predator-AutoComponents
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components

Sign in to add a comment