Predator and CL could not provide any possible suspects.

Using Code Search for the file, "thread_controller_impl.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/d2e82c61666a4be7c5232424d0aab8da01100855

altimin@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

ClusterFuzz has detected this issue as fixed in range 616336:616337.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  test_runner::TestRunner::WorkQueue::ProcessWork
  base::debug::TaskAnnotator::RunTask
  base::sequence_manager::internal::ThreadControllerImpl::DoWork
  
Sanitizer: memory (MSAN)

Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=616336:616337

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

See https://www.chromium.org/developers/testing/memorysanitizer#TOC-Reproducing-ClusterFuzz-Bugs 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 5011936264323072 is verified as fixed, so closing issue as verified.

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