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:

Remove unreachable code in CPDF_DIBBase. by thestig@chromium.org - https://pdfium.googlesource.com/pdfium/+/214982c4d02a720c3b1b3de121cddc62189b8848

Validate more image values in CPDF_DIBBase. by thestig@chromium.org - https://pdfium.googlesource.com/pdfium/+/8590a98297c5a56e63efc63931c1b3998160e049

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 594120:594123.

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

Fuzzer: libFuzzer_pdfium_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  m_pColorSpace
  CPDF_DIBBase::CreateDCTDecoder
  CPDF_DIBBase::CreateDecoder
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=593602:593607
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=594120:594123

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

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.