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

Issue 787378 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Not working on Chrome any more
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

Stack-overflow in blink::StyleBuilder::ApplyProperty

Project Member Reported by ClusterFuzz, Nov 21 2017

Issue description

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

Fuzzer: mbarbella_js_mutation_layout
Job Type: windows_asan_content_shell
Platform Id: windows

Crash Type: Stack-overflow
Crash Address: 0x003a2000
Crash State:
  blink::StyleBuilder::ApplyProperty
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=514498:517698

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Nov 21 2017

Components: Blink>CSS
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 shend@chromium.org, Nov 21 2017

Cc: rjwright@chromium.org
Owner: meade@chromium.org
Status: Assigned (was: Untriaged)
Assigning meade@ and cc'ing rjwright@ based on the suspect CL list.

Comment 3 by shend@chromium.org, Nov 21 2017

Labels: Update-Weekly

Comment 4 by meade@chromium.org, Nov 22 2017

Status: WontFix (was: Assigned)
The test case for this looks like the JS is recursing a lot, and we happen to stack overflow out in some style code. I'd say that's wontfix.

Comment 5 by meade@chromium.org, Nov 22 2017

Labels: ClusterFuzz-Ignore
Project Member

Comment 6 by ClusterFuzz, Nov 29 2017

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