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

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

It's a race on reading and writing write_index_, which is the same underlying cause as in  issue 786829 .

ClusterFuzz has detected this issue as fixed in range 519715:519769.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race WRITE 4
Crash Address: 0x7b3c00001cb0
Crash State:
  blink::RealtimeAnalyser::WriteInput
  blink::AnalyserHandler::Process
  blink::AudioHandler::ProcessIfNecessary
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=473110:473113
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=519715:519769

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

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.