Using the provided regression range assigning to the possible suspect as per the change made for the file, “deflate_set_dictionary_fuzzer.cc”
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/425d4cd82b3cdee276acf851d46d3eaf7662946a

@cblume  -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

Thanks!

I believe that was fixed over here, but was given the wrong bug:
https://chromium-review.googlesource.com/c/chromium/src/+/769155

ClusterFuzz has detected this issue as fixed in range 516865:516900.

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

Fuzzer: libFuzzer_zlib_deflate_set_dictionary_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  false
  _start
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=513911:513929
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=516865:516900

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

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

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