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

> This issue looks similar to  bug 793573 , hence assigning to the same dev for more updates on this issue

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

Thanks!

I'm not the best person to look at this. I owned  Issue 793573  due to Mac triage, but it was closed without my intervention and I have no expertise in this area.

ClusterFuzz has detected this issue as fixed in range 558997:558998.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  test_runner::MockWebSpeechRecognizer::PostRunTaskFromQueue
  base::debug::TaskAnnotator::RunTask
  blink::scheduler::internal::ThreadControllerImpl::DoWork
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=535692:535694
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=558997:558998

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

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

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