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:

JS exposure of feature policy by loonybear@chromium.org - https://chromium.googlesource.com/chromium/src/+/f4bdf01c99906c9f59d8e6ea4993562860ab7d3d

Fixed bug where PlzNavigate CSP in a iframe did not get the inherited CSP by andypaicu@chromium.org - https://chromium.googlesource.com/chromium/src/+/209f225b2d51334eaf69ffdf002e25eaa1e0d448

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

I've had a look and I can't really see my CL causing this DCHECK fail.

As it looks XSLT issue, removing Blink>DOM.
Lowering priority.

loonybear@ Could you please look into this issue.

taking a look

ClusterFuzz has detected this issue as fixed in range 538633:538636.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900000007
Crash State:
  blink::Document::Shutdown
  blink::XSLTProcessor::CreateDocumentFromSource
  blink::DocumentXSLT::ApplyXSLTransform
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=518240:518474
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=538633:538636

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

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

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