Predator and CL did not provide any possible suspect.
Using Code Search for the file, "Document.cpp" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/84834d7d0a7444ae10fb7c49161e1f825558c3ac

@wittman -- Could you please look into the issue, kindly re-assign if this has nothing to do with your changes.
Thank You.

To blink triage.

This looks like Squad territory to me. @nainar could you please have a look and reassign if unrelated?

The suspected change list is too old to be Squad related. Assigning to Layout TL for further triage. 

Triggered a regression analysis yesterday and it still hasn't gotten back. Will keep an eye on it.

Unable to repro and clusterfuzz can't find a regression range. Closing as it is not a security issue.

ClusterFuzz has detected this issue as fixed in range 477767:477864.

Detailed report: https://clusterfuzz.com/testcase?key=4822808925569024

Fuzzer: bj_broddelwerk
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !node.needsStyleRecalc() in Document.cpp
  blink::assertLayoutTreeUpdated
  blink::Document::updateStyleAndLayoutTree
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=338684:338804
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=477767:477864

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4822808925569024


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.