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 blink team to look in to this issue.

Thanks!

ClusterFuzz has detected this issue as fixed in range 566300:566302.

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

Fuzzer: attekett_surku_fuzzer
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  blink::Node::SetNonAttachedStyle
  blink::Element::RecalcStyleForReattach
  blink::ContainerNode::RecalcDescendantStylesForReattach
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=566300:566302

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

See https://github.com/google/clusterfuzz-tools for more information.

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

ClusterFuzz testcase 4927631452274688 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.