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

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

ClusterFuzz has detected this issue as fixed in range 512265:512297.

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

Fuzzer: inferno_webbot
Job Type: windows_syzyasan_chrome
Platform Id: windows

Crash Type: Null-dereference
Crash Address: 0x0000000b
Crash State:
  net::HttpResponseHeaders::FindHeader
  net::HttpResponseHeaders::EnumerateHeader
  data_reduction_proxy::GetDataReductionProxyActionValue
  
Memory Tool: SYZYASAN

Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_chrome&range=511761:511778
Fixed: https://clusterfuzz.com/revisions?job=windows_syzyasan_chrome&range=512265:512297

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

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.