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

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

Can't reproduce this locally.

ClusterFuzz has detected this issue as fixed in range 579361:579363.

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

Fuzzer: libFuzzer_pdfium_xfa_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  TryVSWPrintf
  fxcrt::WideString::FormatV
  CFXJSE_FormCalcContext::ThrowException
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=555725:555734
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=579361:579363

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

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.

ClusterFuzz testcase 6190214842941440 is verified as fixed, so closing issue as verified.

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