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

Author: alokp
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/a04226e0012f12397a1f653dd264b7849112def2
Time: Wed Mar 08 17:01:43 2017
Lines 152-159 of file MojoHandle.cpp which potentially caused crash are changed in this cl (frame #2, "blink::MojoHandle::writeData").
Minimum distance from crash line to modified line: 0. (file: MojoHandle.cpp, crashed on: 149, modified: 149).

@alokp -- 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 500110:500145.

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

Fuzzer: inferno_twister
Job Type: mac_asan_content_shell
Platform Id: mac

Crash Type: Floating-point-exception
Crash Address: 
Crash State:
  mojo::edk::DataPipeProducerDispatcher::WriteData
  mojo::edk::Core::WriteData
  blink::MojoHandle::writeData
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=455449:455516
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=500110:500145

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

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

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