Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Unable to find actual suspect through code search and also observing no related changes under regression range, hence adding appropriate label and requesting someone from network team to look in to this issue.

Thanks!

I'll take a look.

This crash was not reproducible either locally or using the downloaded build using the reproducer. My cmd line flag was:
/google/data/ro/teams/clusterfuzz-tools/releases/clusterfuzz reproduce 5324905865019392 --disable-xvfb

(with separately --build download)

I'll re-do the clusterfuzz task.

ClusterFuzz has detected this issue as fixed in range 553139:553151.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  content::ResourceDispatcherHostImpl::PickMoreInterestingLoadInfos
  content::ResourceDispatcherHostImpl::UpdateLoadStateOnUI
  void base::internal::FunctorTraits<void
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=546471:546478
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=553139:553151

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

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 5324905865019392 is verified as fixed, so closing issue as verified.

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

Fix range also doesn't make much sense :/