Through code search file 'file_tracing.cc' suspecting the below
https://chromium.googlesource.com/chromium/src/+/fd5b108c82d56f6022dfbe62a023d1e81ff6f83b%5E%21/base/files/file_tracing.cc

dbeam@ Could you please look into this issue if its related to your change,else please re assign it to an appropriate dev person.

ClusterFuzz has detected this issue as fixed in range 389097:389209.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6400996950933504

Fuzzer: attekett_dom_fuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race on vptr READ 8
Crash Address: 0x7d0400002ea0
Crash State:
  base::FileTracing::IsCategoryEnabled
  base::File::Initialize
  base::File::File
  
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_tsan_chrome_mp&range=389097:389209

Minimized Testcase (0.06 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv95h6m1APQyTelKhOqu9tpxGB_ffalmEYWZrXu_ppM6Mn_8fD2ShD6CAdwwwAhjksEo2rGjhJFWtZclKMtHLmJnUxXkjiADLxrKYYMWO5TdYtJYT5kuJFHEcNj5hXOCM4ZHF3O-gjlZ__WHF_CNV-AmFkxIi7w
<img src="https://bugs.webkit.org/attachment.cgi?id=112157">


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot