Automatically adding ccs based on suspected regression changelists:

Tweak per-face LCD filtering controls. by apodtele@gmail.com - https://chromium.googlesource.com/chromium/src/third_party/freetype2/+/02e80da6090c21d6e59ac955b7f56e1ad4a9850b

[smooth, raster] Miscellaneous cleanups. by apodtele@gmail.com - https://chromium.googlesource.com/chromium/src/third_party/freetype2/+/ae7dc1f62d826083d418e86cce3f66a76dff038a

Bitmap metrics presetting [1/2]. by apodtele@gmail.com - https://chromium.googlesource.com/chromium/src/third_party/freetype2/+/61d1818b5ef4fd9b014c4577f07cf5580ba67eee

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

I think pdfium_fuzzer ended up fuzzing FreeType here.

with reference to the  Issue 778945 , marking this issue as Won't Fix
Please undo it, if it not the case

ClusterFuzz testcase 6697412450844672 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

ClusterFuzz has detected this issue as fixed in range 565878:565882.

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

Fuzzer: libFuzzer_pdfium_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  pdfium_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=509045:509075
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=565878:565882

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

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.