Suspected CL could be
https://chromium.googlesource.com/chromium/src/+/99d88a6fd4fed13ef44a24800f2bf79da69abc7e%5E%21/third_party/WebKit/Source/core/fetch/ResourceFetcher.cpp

Last updated by japhet @ weeks ago , please have a look and reassign if needed.

Thank you.

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

Fuzzer: afl_renderer_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  blink::TimerBase::TimerBase
  blink::ResourceFetcher::ResourceFetcher
  blink::ResourceFetcher::create
  

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97iE8ve9MASSzl-nTf1QQCVIbBJKFT0WUXmqvUxOwajglmTRbRplPh1LFehT4LwP8XTCde5a2dWdDJM6RH34lWEUp93H-P15Bc-pRjkrZ6CyxEVQyYEx_iuvUyU_0h_xTJPj32FaUcjTtVs5H0T3y9DG4FEYw?testcase_id=5929631802982400


Filer: mmohammad

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

I think I ran this test correctly locally, but I wasn't able to reproduce the crash.

Given the nature of it, I'm strongly suspicious that it's a test harness problem rather than a production bug.

Ok, clusterfuzz couldn't repro either. Closing.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot