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

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

This is probably a duplicate of  bug 830221 . I don't know why CF even bothered reporting it at r543766 when ToT is 30K commits ahead.

+ochang@, CF sheriff this week.

Somehow corpus pruning ran on an ancient revision. Filed https://bugs.chromium.org/p/chromium/issues/detail?id=856906 to track this.

ClusterFuzz has detected this issue as fixed in range 549809:549820.

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

Fuzzer: libFuzzer_pdfium_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffd630caea8
Crash State:
  CPDF_StitchFunc::v_Init
  CPDF_Function::Init
  CPDF_Function::Load
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=395675:395769
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=549809:549820

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

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.