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:

Cleanup CFX_XMLParser entity conversion by dsinclair@chromium.org - https://pdfium.googlesource.com/pdfium/+/8a95c22dd5d4f7d4e730370c761f41298ba98bf2

Remove CFX_BlockBuffer by dsinclair@chromium.org - https://pdfium.googlesource.com/pdfium/+/6453a67d84dc321a5f28728e04929dc2ff35ff88

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

ClusterFuzz has detected this issue as fixed in range 554213:554246.

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

Fuzzer: libFuzzer_pdf_xml_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Ill
Crash Address: 0x000000451250
Crash State:
  pdf_xml_fuzzer
  pdfium::base::internal::StrictNumeric<unsigned long> pdfium::base::internal::Che
  fxcrt::StringDataTemplate<wchar_t>::Create
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=553241:553259
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=554213:554246

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.