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

Issue 747659 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Stack-overflow in blink::LayoutBox::AvailableLogicalHeightUsing

Project Member Reported by ClusterFuzz, Jul 22 2017

Issue description

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

Fuzzer: inferno_layout_test_unmodified
Job Type: mac_asan_content_shell
Platform Id: mac

Crash Type: Stack-overflow
Crash Address: 0x7fff5f14bfe0
Crash State:
  blink::LayoutBox::AvailableLogicalHeightUsing
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=486793:486853

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


Issue filed automatically.

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

Comment 1 by tapted@chromium.org, Jul 24 2017

Components: Blink>Layout
Cc: msrchandra@chromium.org
Labels: M-62 Test-Predator-Wrong
Owner: e...@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL did not provide any possible suspects.
Using Code Search for the file, "LayoutBox.cpp" assigning to the concern owner.

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

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

Comment 3 by e...@chromium.org, Jul 31 2017

Status: WontFix (was: Assigned)
Project Member

Comment 4 by ClusterFuzz, Aug 5 2017

Labels: OS-Linux
Project Member

Comment 5 by ClusterFuzz, Aug 7 2017

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