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 suspected 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 568005:568006.

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

Fuzzer: attekett_dom_fuzzer
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  IsBeforePseudoElement() || IsAfterPseudoElement() || GetPseudoId() == kPseudoIdB
  blink::Element::StyleForLayoutObject
  blink::Element::RecalcOwnStyle
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=331388:331413
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=568005:568006

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

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

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