CHECK failure: lifecycle_.GetState() >= DocumentLifecycle::kStyleClean in document.cc |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4697934728527872 Fuzzer: ifratric-browserfuzzer-v3 Job Type: linux_debug_chrome Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: lifecycle_.GetState() >= DocumentLifecycle::kStyleClean in document.cc blink::Document::ScrollingElementNoLayout blink::Document::scrollingElement Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4697934728527872 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Oct 16
,
Oct 19
,
Dec 15
ClusterFuzz has detected this issue as fixed in range 616959:616960. Detailed report: https://clusterfuzz.com/testcase?key=4697934728527872 Fuzzer: ifratric-browserfuzzer-v3 Job Type: linux_debug_chrome Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: lifecycle_.GetState() >= DocumentLifecycle::kStyleClean in document.cc blink::Document::ScrollingElementNoLayout blink::Document::scrollingElement Sanitizer: address (ASAN) Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=616959:616960 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4697934728527872 See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Dec 15
ClusterFuzz testcase 4697934728527872 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by kkaluri@chromium.org
, Oct 3Labels: M-71 Test-Predator-Wrong CF-NeedsTriage
Owner: infe...@chromium.org
Status: Assigned (was: Untriaged)