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 suspected regression changelists:

Move replaying of redirects and response started to ResourceDispatcher by jcivelli@google.com - https://chromium.googlesource.com/chromium/src/+/a9d4f3475db7300488ccf1c4d2f0cfb7ce9ef1fd

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

jcivelli@ Would you mind taking a look in to this issue?

Thanks!

I have a fix up for review https://chromium-review.googlesource.com/c/chromium/src/+/1003316

ClusterFuzz has detected this issue as fixed in range 549649:549652.

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

Fuzzer: meacer_web_ext
Job Type: linux_asan_chrome_mp
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x0000000000a0
Crash State:
  content::ThrottlingURLLoader::FollowRedirect
  content::WebURLLoaderImpl::Context::SetDefersLoading
  blink::ResourceLoader::SetDefersLoading
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=548788:548789
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=549649:549652

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

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.

ClusterFuzz testcase 6501213252878336 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.