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 adding ccs based on suspected regression changelists:

Refactors ensureUpToDate to use rAF callback. by meredithl@google.com - https://chromium.googlesource.com/chromium/src/+/e35fb3af9c9e2ce800e8f5c9bca93cb650c6f738

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

The problem seems to be

https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/dom/computed_accessible_node.cc?q=symbol:%5Eblink::ComputedAccessibleNodePromiseResolver::UpdateTreeAndResolve$&sq=package:chromium&g=0&l=83

void ComputedAccessibleNodePromiseResolver::UpdateTreeAndResolve() {
  LocalFrame* local_frame = element_->ownerDocument()->GetFrame();
  WebFrameClient* client = WebLocalFrameImpl::FromFrame(local_frame)->Client();

since GetFrame may return nullptr (e.g. if the document has been constructed via JS).

Predator and CL could not provide any possible suspects.
Using the code search for the file, “computed_accessible_node.cc” assigning to concern owner from GIT revision log.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/06bafdfb50ee7ede3709742290c256e60ad50bdb

@aboxhall -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

ClusterFuzz testcase 5167909203345408 appears to be flaky, updating reproducibility label.

ClusterFuzz testcase 5167909203345408 is flaky and no longer crashes, so closing issue.

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