Stack-overflow in blink::LayoutBlockFlow::UpdateBlockLayout |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5050357817540608 Fuzzer: inferno_layout_test_unmodified Job Type: mac_asan_chrome Platform Id: mac Crash Type: Stack-overflow Crash Address: 0x7fff5d398e00 Crash State: blink::LayoutBlockFlow::UpdateBlockLayout blink::LayoutBlock::UpdateLayout blink::LayoutBlockFlow::PositionAndLayoutOnceIfNeeded Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=436323:436519 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5050357817540608 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Sep 7 2017
Predator and CL could not provide any possible suspects. Using Code Search for the file, "LayoutBlockFlow.cpp" assigning to the concern owner. Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/24bd4066e46f42bdafe467100538f4c6e940ff55 @yoichio -- Could you please look into the issue, kindly re-assign if this is not related to your changes. Thank You.
,
Sep 7 2017
My change is just revert.
,
Sep 7 2017
@yoichio -- Thank you for the update.
,
Sep 7 2017
Deeply nested content. WontFix.
,
Sep 15 2017
ClusterFuzz testcase 5050357817540608 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 |
||||||
Comment 1 by ClusterFuzz
, Sep 7 2017