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 assigning owner based on suspected regression changelist https://pdfium.googlesource.com/pdfium/+/c0043a8ccdf0768c2bd285f90e730645cb38a0c7 (Validate the Range key in Functions.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

 Issue 835105  has been merged into this issue.

Reverted for now. https://pdfium.googlesource.com/pdfium/+/e61e2f3d34efee51b69838646dd4e7462989ca08

 Issue 835212  has been merged into this issue.

 Issue 835230  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 552285:552288.

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

Fuzzer: ifratric_pdf_generic
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000000
Crash State:
  raise
  GetBits32
  CPDF_SampledFunc::v_Call
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=552137:552140
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=552285:552288

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

See https://github.com/google/clusterfuzz-tools 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 5270660008640512 is verified as fixed, so closing issue as verified.

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