Assigning to the concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: kinuko
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/2a4d9d1f74a04c1122bc7ca32027da87cb14d3bd
Time: Thu Feb 23 11:14:07 2017
Lines 238 of file WorkerThreadableLoader.cpp which potentially caused crash are changed in this cl (frame #3, "blink::WorkerThreadableLoader::start").
Minimum distance from crash line to modified line: 0. (file: WorkerThreadableLoader.cpp, crashed on: 238, modified: 238).

@kinuko -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Assigning to the concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: kinuko
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/2a4d9d1f74a04c1122bc7ca32027da87cb14d3bd
Time: Thu Feb 23 11:14:07 2017
Lines 238 of file WorkerThreadableLoader.cpp which potentially caused crash are changed in this cl (frame #3, "blink::WorkerThreadableLoader::start").
Minimum distance from crash line to modified line: 0. (file: WorkerThreadableLoader.cpp, crashed on: 238, modified: 238).

@kinuko -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

ClusterFuzz has detected this issue as fixed in range 491526:491565.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race READ 8
Crash Address: 0x7b3c0001a9c8
Crash State:
  void base::internal::FunctorTraits<void
  base::internal::Invoker<base::internal::BindState<void
  blink::runCrossThreadClosure
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=452175:452475
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=491526:491565

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


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

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