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

Author: yosin
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/2211504ac2b999a125b2215ce7f6be9e50878fea
Time: Thu Mar 02 12:28:15 2017
Lines 63-64 of file PositionIterator.cpp which potentially caused crash are changed in this cl (frame #3, "blink::PositionIteratorAlgorithm >::PositionIteratorAlgorithm"). 

Lines 2903 of file VisibleUnits.cpp which potentially caused crash are changed in this cl (frame #4, "mostBackwardCaretPosition >").
Minimum distance from crash line to modified line: 0. (file: PositionIterator.cpp, crashed on: 64, modified: 64).

@yosin -- 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 455091:455394.

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

Fuzzer: bj_broddelwerk
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000010
Crash State:
  blink::FlatTreeTraversal::traverseChild
  traverseFirstChild
  blink::FlatTreeTraversal::childAt
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=454233:454299
Fixed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=455091:455394

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv97izHmUygTWswdLocQqj6ow-XWx_qFJaS45r7ZXzsXCkk6dvDiMEn5vdpjzyadOzRkbIjDpXuAFVklOWgX6S7m2xvPxGZ02zc61Af5SjJwGqFZ6XpVjcxItPnRcK-gqqGAsTjJ5SO2DwbCO-7DFdC1ph1Ol607oC11nSsjoAOYtCVWDUmgrbaybnkz2y3gSjog0urkR6g2vQXlv_Uc065Z52kWveZTeKA3bnLyji9ix6pYKOXxMHZ2_FZmN32fSyyr_Xrkh0HurmXZEoEVl11eTOMnB-mEhud015AEcC65Z_uM54em5eVP22c5OVF0L9B72ji30DuLiCxvDkSW6shpC_iGgJmWXFXK22z_MHc7YO4oyJ3o?testcase_id=6071560340504576


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

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