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

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

As per the  Issue 724974  owner, assigning this issue to @lushnikov.
@lushnikov -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thanks.

Doesn't reproduce for me on a new testing framework.

ClusterFuzz testcase 4526247341457408 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

ClusterFuzz has detected this issue as fixed in range 526106:526107.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::DOMPatchSupport::CreateDigest
  blink::DOMPatchSupport::PatchDocument
  blink::InspectorDOMAgent::setOuterHTML
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=473072:473106
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=526106:526107

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

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.