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

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

Unable to find actual suspect through code search and also observing no related changes under regression range, hence adding appropriate label and requesting someone from UI team to look in to this issue.

Thanks

ClusterFuzz has detected this issue as fixed in range 553139:553151.

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

Fuzzer: inferno_flicker
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race WRITE 4
Crash Address: 0x555ea49fe5f0
Crash State:
  gfx::SetFontRenderParamsDeviceScaleFactor
  views::DesktopScreenX11::UpdateDisplays
  base::internal::Invoker<base::internal::BindState<void
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=546649:546656
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=553139:553151

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

Additional requirements: Requires Gestures

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

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