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.

> By comparing the stack trace of this issue, it looks similar to  bug 829067  , hence assigning to the same owner for more updates.

> csharrison@ Could you please take a look in to this issue?

Thanks!

+mbarbella, this is an example of a bug report with a confusing regression range in the past. According to the fuzzer this is not fixed, but it regressed 3 months ago.

It also looks like this report has a heap-use-after-free immediately before the crash. Possibly that is the culprit here.

There is probably the same root issue as  issue 829067 , but I'll hold off duping them for now since the reports are different.

ClusterFuzz has detected this issue as fixed in range 584882:584885.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_tsan_chrome_mp
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=528051:528053
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=584882:584885

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

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

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