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

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

Nicolas, can you take a look?

Assigning all my PDF bugs to dsinclair@ for triaging. Will not be working on PDFium for a month.

ClusterFuzz has detected this issue as fixed in range 552911:552920.

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

Fuzzer: libFuzzer_pdf_codec_jbig2_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  CJBig2_Context::huffman_assign_code
  CJBig2_Context::decodeSymbolIDHuffmanTable
  CJBig2_Context::parseTextRegion
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=421422:421461
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=552911:552920

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

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

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

Likely https://pdfium.googlesource.com/pdfium/+/cca452eab645fd6b0e63ab2fd1dd553277df111e stopped the integer overflow by limiting image sizes.