Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

This issue looks similar to  bug 842529 , hence assigning to the same owner for more updates.

dsinclair@ Could you please take a look in to this issue?

Thanks!

ClusterFuzz has detected this issue as fixed in range 563014:563041.

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

Fuzzer: libFuzzer_pdfium_xfa_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  _IO_wdefault_xsputn
  vfwprintf
  vswprintf
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=562400:562409
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=563014:563041

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

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

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

I suspect CF is being flaky and this will just crop up again as a different bug.

Setting PDF bugs assigned to me back to untriaged so they can get re-assigned as needed.

ClusterFuzz testcase 5562318130511872 appears to be flaky, updating reproducibility label.

ClusterFuzz testcase 5562318130511872 is flaky and no longer crashes, so closing issue.

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