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, "crash_logging.cc" and observed there was some recent changes for the below file.

Suspect CL: https://chromium.googlesource.com/chromium/src/+/5799f48f4759cc4e47125f35310d266253f659f6

rsesek@ -- 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 532723:532725.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race WRITE 1
Crash Address: 0x7bb400001998
Crash State:
  crash_reporter::internal::CrashKeyStringImpl::Set
  crash_reporter::CrashKeyBaseSupport::Set
  base::debug::SetCrashKeyString
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=525012:525018
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=532723:532725

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

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.