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:

Rework of CPDF_Parser::RebuildCrossRef. by art-snake@yandex-team.ru - https://pdfium.googlesource.com/pdfium/+/c68109a2dac3be544b7753d1fd677255d859745b

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

With reference to the  Issue 875282 , assigning it to thestig@

ClusterFuzz has detected this issue as fixed in range 598252:598253.

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

Fuzzer: libFuzzer_pdfium_xfa_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  CFX_RTFBreak::AppendChar_Others
  CFX_RTFBreak::AppendChar
  CXFA_TextLayout::AppendChar
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=576839:576840
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=598252:598253

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

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

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

Not fixed. I broke the fuzzer.