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/+/4db9046e56c884a350fa2c5087f8d5b8110463c4 (Add heuristic for improving text rendering in CPDF_CharPosList::Load).

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.

ClusterFuzz has detected this issue as fixed in range 533124:533148.

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

Fuzzer: libFuzzer_pdfium_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  scalingFactor >= 0.0f
  CPDF_CharPosList::Load
  CPDF_TextRenderer::DrawNormalText
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=480653:480710
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=533124:533148

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

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

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

This was probably fixed by https://pdfium-review.googlesource.com/c/pdfium/+/24410.

Yea... my CL had the bug ID but the bot was too lazy to report it.