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 CL under regression range, hence adding appropriate label and requesting someone from internals team to look in to this issue.

Thanks!

ClusterFuzz has detected this issue as fixed in range 560278:560283.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  base::RunLoop::Run
  base::Thread::ThreadMain
  base::ThreadFunc
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=560278:560283

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

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

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

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

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