CHECK failure: Lifecycle().StateAllowsTreeMutations() in Document.cpp |
||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4985557219016704 Fuzzer: mbarbella_js_mutation_layout Job Type: linux_msan_content_shell_drt Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: Lifecycle().StateAllowsTreeMutations() in Document.cpp blink::Document::UpdateStyleAndLayoutTreeIgnorePendingStylesheets blink::Document::UpdateStyleAndLayoutIgnorePendingStylesheetsForNode Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=539777:539778 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4985557219016704 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Mar 25 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/b2d7c2e28ac266e5adfcfad9f38268a4f774bf91 (getCapabilities() should not have range properties without valid values). 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.
,
Mar 26 2018
The call stack does not relate to the changes in the suspected CL. As per the callstack, the crash seems to be due to below CHECK failure [1:1:0325/062343.981010:FATAL:Document.cpp(2416)] Check failed: Lifecycle().StateAllowsTreeMutations(). However, the suspected CL does not have any change related to this. It seems like this CL has been wrongly picked.
,
Mar 26 2018
Removing c.padhi@ as owner as per #3 and leaving untriaged for the right component owners to triage. cc chrishtr@, since this is apparently crashing on a CHECK added in r487157, authored by him.
,
Mar 27 2018
,
Mar 27 2018
Since the testcase is about Custom Paint, we're moving it from Blink>DOM to Blink>Paint (hit the send button too early)
,
Mar 27 2018
Assigned right for Custom Paint?
,
Mar 27 2018
Cannot repro this locally with the CFI repro tool, I am kicking off another run.
,
Apr 3 2018
Not able to repro it locally with -b=download and -b=chromium, from the report page it appears that there is no crash in the last 7 days. So closing this bug as won't fix.
,
Apr 10 2018
ClusterFuzz testcase 4985557219016704 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
, Mar 25 2018Labels: Test-Predator-Auto-Components