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

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

Predator and CL could not provide any possible suspects.
Using the code search for the file, “thread_controller_impl.cc” assigning to concern owner from GIT blame.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/01521901c75de270189594fa8c746c8ae31da913

@alexclarke -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

Perhaps lukasza@ might be better placed to triage this?

ClusterFuzz has detected this issue as fixed in range 567493:567494.

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

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
  base::sequence_manager::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=567493:567494

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

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

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