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 Code Search for the file, "worker_thread.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/625d998496348a053dd112fc5b6c09364633882e

yutak@ -- 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 602151:602152.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  started in worker_thread.cc
  blink::scheduler::WorkerThread::WorkerThread
  blink::Platform::CreateThread
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=601980:601982
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=602151:602152

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

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

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