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

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/0fd72b878bb8e5fef918b9a836d760d6cecc4150 (Add Assign function).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

I couldn't repro this. The repro case is too huge.
Given that CL is unlikely to the cause, and this crash is similar to bug 762931,
let's merge this into that.

ClusterFuzz has detected this issue as fixed in range 583238:583249.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_cfi_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000010
Crash State:
  blink::LiveNodeListBase::InvalidateCacheForAttribute
  blink::NodeListsNodeData::InvalidateCaches
  blink::ContainerNode::InvalidateNodeListCachesInAncestors
  
Sanitizer: cfi (CFI)

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=583177:583181
Fixed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=583238:583249

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

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.