CHECK failure: i < size() in vector.h |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5341362971738112 Fuzzer: inferno_layout_test_unmodified Job Type: linux_asan_content_shell_drt Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: i < size() in vector.h blink::LayoutTable::UpdateLayout blink::LayoutBlockFlow::PositionAndLayoutOnceIfNeeded Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=545879:545880 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5341362971738112 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Apr 19 2018
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Apr 19 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/279708b3c8ed5b6d9b4ed452072458cb0f9047d0 ([LayoutTests] Replace multiple dump responses with one callback/struct.). 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.
,
Apr 19 2018
Can't seem to preproduce on ToT. It's unlikely that the patch in question caused the regression, since it's coming from a layout test only code which shouldn't affect how layout is done. The check seems to be in layout code. I'm going to forward to eae@ for triage. For completeness, this is in table layout code on vector access. I took a look at the code and it doesn't seem suspicious..
,
Apr 19 2018
,
Apr 26 2018
ClusterFuzz testcase 5341362971738112 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
, Apr 19 2018