Based on Predator results, assigning to haraken@ - could you please check the issue and help.

The result is a list of CLs that change the crashed files. 

Author: haraken
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/89d59827bf8706769513e1b6b0ad1a113bbfa65d
Time: Wed Feb 08 19:50:41 2017
Lines 247-248 of file ThreadState.cpp which potentially caused crash are changed in this cl (frame #4, "blink::ThreadState::runTerminationGC").
Minimum distance from crash line to modified line: 0. (file: ThreadState.cpp, crashed on: 248, modified: 248).

ClusterFuzz has detected this issue as fixed in range 449378:449549.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race ATOMIC WRITE 8
Crash Address: 0x7b18000118c8
Crash State:
  blink::PersistentBase<blink::WorkerGlobalScope,
  blink::InProcessWorkerObjectProxy::willDestroyWorkerGlobalScope
  blink::WorkerThread::prepareForShutdownOnWorkerThread
  
Sanitizer: thread (TSAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_tsan_chrome_mp&range=449020:449079
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_tsan_chrome_mp&range=449378:449549

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv941IsRPPac9-nl-pzg8-uOh6AplcjU0n0bwGHnQxMJmxyCPaJaGi__CyXU60D_gYhBSA2Sh_FxQXnZZ4UNPpvWsPYVuBOysyp7w2kdv-O6Lp1zyaKJbDM1owMVwEF7cudnLqYOO8jel-gZlHU1_pRXi2cX9LtLhsd1T_Si4Dsqqy9u2InkVZkQnq6XA4by4MevNzEVsGbMs-PaoDZw7-Cl1EEqo1u0ncvEvWhOETZvpSfrjoNb54iBAx4CzO2DfCP9BFr0BBH03CU_TxPsClMJ2N4QQMSG61dljhdBdhS7nAJGbNnF-3EgLhVZBB8tNLPlmCbxcCrEIIO6Tj1H2kePFrZT9en4gzXlnrVrTeBsvQ9cXAncARruE4mp1-85nVGCa4iT6NhlnivrSWjG9kqXZYtHnlg?testcase_id=4717191946829824


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.

ClusterFuzz testcase 4717191946829824 is verified as fixed, so closing issue.

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