Through code search on file host_resolver_impl.cc, suspected CL is https://chromium.googlesource.com/chromium/src/+/d6e9161aff5787fa445cbbbdf8dbc48ac95d38ac
mmenke@, could you please take a look and help us to find correct owner if it is not related your changes.

"Internals>Compositing"?

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2f23b702967fc351f90a8274c6df03054fa23234

commit 2f23b702967fc351f90a8274c6df03054fa23234
Author: mmenke <mmenke@chromium.org>
Date: Wed Oct 26 23:26:42 2016

Fix DNS logging macro that was broken by adding another net priority.

This was broken by https://codereview.chromium.org/1866483002/

BUG= 600839 , 659338 

Review-Url: https://codereview.chromium.org/2452863003
Cr-Commit-Position: refs/heads/master@{#427874}

[modify] https://crrev.com/2f23b702967fc351f90a8274c6df03054fa23234/net/dns/host_resolver_impl.cc

No need to restrict this - in release bugs, it's just a harmless DCHECK, following by not incrementing any UMA histogram bucket.

ClusterFuzz has detected this issue as fixed in range 427846:427885.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5072577870692352

Fuzzer: libfuzzer_net_host_resolver_impl_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e9000047eb
Crash State:
  base::debug::DebugBreak
  net::HostResolverImpl::Job::Start
  net::PrioritizedDispatcher::Add
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=426787:426846
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=427846:427885

Minimized Testcase (0.00 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97gnlVk1ymxC7HnhwpkCufpR-4eFs3iUjDZwzYL8flFApt8mSTB21-XEcUqlkoO_rbNbYSvrCIIwTI5txLsm0fASklkG_gkMc5HwP7-Ehe3xOBXjXpeqcMJ_sHy503v7GOIIX6fzdlGxqEmq9kQOGGmQD-Yog?testcase_id=5072577870692352

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.