CHECK failure: float_logical_location.Y() == new_logical_top_margin_edge in layout_block_flow.c |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6098912671432704 Fuzzer: bj_broddelwerk Job Type: linux_debug_chrome Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: float_logical_location.Y() == new_logical_top_margin_edge in layout_block_flow.c blink::LayoutBlockFlow::PositionAndLayoutFloat blink::LineLayoutBlockFlow::PositionAndLayoutFloat Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6098912671432704 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jun 29 2018
Unable to find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label and requesting someone from Android team to look in to this issue. Thanks!
,
Jul 1
Not a security issue and no reports in the wild. As this code is being replaced by LayoutNG it doesn't seem worth the effort to look into it.
,
Jul 8
ClusterFuzz testcase 6098912671432704 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
, Jun 28 2018Labels: Test-Predator-Auto-Components