Test Predator has given the following results:

HostResolverImpl fuzzer fixes by mgersh@chromium.org

Minimum distance between changed lines and stacktrace lines in host_resolver_impl_fuzzer.cc is 10
Top touched frame is #5 (in host_resolver_impl_fuzzer.cc)
Changed files host_resolver_impl_fuzzer.cc, with the same CrashedDirectory(net/dns) as host_resolver_impl_fuzzer.cc (in frame#5, frame#6)
Touched files in stacktrace - host_resolver_impl_fuzzer.cc
Changed files host_resolver_impl_fuzzer.cc, with the same CrashedComponent(Internals>Network>DNS) as host_resolver_impl_fuzzer.cc (in frame#5, frame#6)

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

Thank You.

ClusterFuzz has detected this issue as fixed in range 504110:504235.

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

Fuzzer: libFuzzer_net_host_resolver_impl_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  request_ in host_resolver_impl_fuzzer.cc
  DnsRequest::WaitUntilDone
  DnsRequest::WaitForRequestComplete
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=503743:503814
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=504110:504235

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.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 4924859187724288 is verified as fixed, so closing issue as verified.

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