Stack-overflow in blink::LayoutBlock::UpdateLayout |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5662675503415296 Fuzzer: inferno_layout_test_unmodified Job Type: mac_asan_content_shell Platform Id: mac Crash Type: Stack-overflow Crash Address: 0x7fff58f0dbd8 Crash State: blink::LayoutBlock::UpdateLayout blink::LayoutBlockFlow::PositionAndLayoutFloat blink::LayoutBlockFlow::PlaceNewFloats Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=614365:614378 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5662675503415296 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
,
Dec 31
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/43a377d1697ac74ec5e45f739ee90becbcf253df ([DL] Don't immediately update the locked element frame rect.). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Jan 2
Unlikely to be the patch in #2. This is a fuzz stack overflow, so I would suspect it's a won't fix.
,
Jan 2
Indeed, stack overflow due to a very deep DOM. Thanks vmpstr.
,
Jan 9
ClusterFuzz testcase 5662675503415296 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.
,
Jan 15
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ClusterFuzz
, Dec 31Labels: Test-Predator-Auto-Components