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://chromium.googlesource.com/chromium/src/+/01d1d1c15c54f84470463190d2da98e5b6755d97 (HostResolverImpl fuzzer fixes).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

My CL was just fixing the fuzzer, it didn't introduce the bug.

This looks like it might be the same crash as  issue 768150 , but I'll have to look at it more to be sure.

Yeah, same crash.

ClusterFuzz has detected this issue as fixed in range 512844:512867.

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

Fuzzer: libFuzzer_net_host_resolver_impl_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000008
Crash State:
  net::DnsTransactionImpl::DoCallback
  base::debug::TaskAnnotator::RunTask
  base::MessageLoop::RunTask
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=503770:503839
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=512844:512867

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

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.