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

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

This issue looks similar to bug 794920, hence merging in to it. Feel free to undupe if it's a different issue.

Thanks!

ClusterFuzz has detected this issue as fixed in range 552291:552292.

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

Fuzzer: inferno_twister_c
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race WRITE 1
Crash Address: 0x7bb400002417
Crash State:
  crash_reporter::internal::CrashKeyStringImpl::Set
  discardable_memory::DiscardableSharedMemoryManager::AllocateLockedDiscardableSha
  discardable_memory::DiscardableSharedMemoryManager::AllocateLockedDiscardableMem
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=536321:536323
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=552291:552292

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

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.