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

Thanks!

ClusterFuzz has detected this issue as fixed in range 560863:560869.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race WRITE 8
Crash Address: 0x7b0c001c66e0
Crash State:
  libdconfsettings.so
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=523888:523922
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=560863:560869

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

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

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