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

Author: nhiroki
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/7800a474d39eacc36c6c247f6a956e15f5d2489a
Time: Thu Apr 20 10:06:51 2017
Lines 209 of file WorkerThread.cpp which potentially caused crash are changed in this cl (frame #0, "blink::WorkerThread::GetIsolate").

Started a minimize task...

ClusterFuzz has detected this issue as fixed in range 467999:468017.

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

Fuzzer: inferno_twister
Job Type: mac_asan_content_shell
Platform Id: mac

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  blink::WorkerThread::GetIsolate
  blink::WorkerGlobalScope::ExceptionUnhandled
  blink::InProcessWorkerObjectProxy::ProcessUnhandledException
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=465961:465971
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=467999:468017

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


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

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

This should be fixed by https://bugs.chromium.org/p/chromium/issues/detail?id=713914#c9