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 adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/916f33589c6e4656f25cb846cbb572191be4fb6a (Move replaying of redirects and response started to ResourceDispatcher).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

I'm re-opening this as it was found with an active fuzz target and looks totally legit.

ClusterFuzz has detected this issue as fixed in range 616459:616466.

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

Fuzzer: libFuzzer_renderer_fuzzer
Fuzz target binary: renderer_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  content::WebURLLoaderImpl::LoadAsynchronously
  blink::ResourceLoader::StartWith
  blink::ResourceLoadScheduler::Run
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=550878:550879
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=616459:616466

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

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.