Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

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

Thanks!

Regarding RecalcStyle, I think Blink>CSS would be better to get attention.

futhark@, This is still happening on M70, can you please take a look?

ClusterFuzz has detected this issue as fixed in range 605493:605497.

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

Fuzzer: attekett_dom_fuzzer
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  blink::Node::SetNonAttachedStyle
  blink::Element::RecalcOwnStyle
  blink::Element::RecalcStyle
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=587598:587602
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=605493:605497

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

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 5649996691800064 is verified as fixed, so closing issue as verified.

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