Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Unable to find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label and requesting someone from Dev team to look in to this issue.

Thanks!

mmoroz@, just wondering do you have any inputs here?

Interesting! Looks like an inputs is too big to process:

$ pngcheck -v clusterfuzz-testcase-minimized-libpng_read_fuzzer-5386974402445312 
File: clusterfuzz-testcase-minimized-libpng_read_fuzzer-5386974402445312 (209705 bytes)
  chunk IHDR at offset 0x0000c, length 13
    253544 x 200 image, 48-bit RGB, non-interlaced
  chunk IDAT at offset 0x00025, length 352326290
    zlib: deflated, 32K window, default compression
:  EOF while reading data

cblume@, since you've been interesting in PNG fuzzing, maybe you could also take a look at this one and e.g. add some limits against super big images?

We have some, but it looks like it can be improved: https://cs.chromium.org/chromium/src/testing/libfuzzer/fuzzers/libpng_read_fuzzer.cc?q=libpng_read_fuz&sq=package:chromium&g=0&l=129

ClusterFuzz has detected this issue as fixed in range 608446:608451.

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

Fuzzer: libFuzzer_libpng_read_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  libpng_read_fuzzer
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=583284:583299
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=608446:608451

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

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

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