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 from the provided CL under regression range, hence adding appropriate label and leaving it as untriaged for further updates.

Thanks!

ClusterFuzz has detected this issue as fixed in range 535924:535929.

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

Fuzzer: attekett_dom_fuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000008
Crash State:
  blink::CachedMatchedProperties::Clear
  blink::MatchedPropertiesCache::Clear
  blink::StyleResolver::InvalidateMatchedPropertiesCache
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=535301:535306
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=535924:535929

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

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.