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

Author: yosin@chromium.org
Project: chromium-blink
Changelist: https://chromium.googlesource.com/chromium/blink.git/+/f95657dc086584f4f821f65b56bcf00fcd6a3499
Time: Mon Apr 13 01:24:17 2015
File TextIterator.cpp is changed in this cl (and is part of stack frame #2, "shadowDepthOf >"; frame #3, "blink::TextIteratorAlgorithm >::initialize"; frame #4, "blink::TextIteratorAlgorithm >::rangeLength")
Minimum distance from crash line to modified line: 10. (file: TextIterator.cpp, crashed on: 129, modified: 139).

@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=4591531706286080

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000020
Crash State:
  treeScope
  shadowDepthOf<blink::EditingAlgorithm<blink::NodeTraversal>
  blink::TextIteratorAlgorithm<blink::EditingAlgorithm<blink::NodeTraversal> >::in
  
Sanitizer: address (ASAN)

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

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv95FQ0cj4x_nBmmC-2Unj0ZWOdGjfRpDQKM6yoYDV-S8hNihVVRGqeLnv71xGoFabstYVJiTXI0k44szr-qTUxw8zLZXYMmBiFZ7xQeDGlyG07_sctX99gjoWLkbdc0bTptmHuwB-7pIS9VDMVxVpwzBD7w9Y6YnWreAGCC4ChpatrBwc2BxWZgSsJeMOmgtMIc6RSGajyCvYKxi5LgP-r8KBKR5NUXMnAjuedDha9ZmvaeCrBHBrvEpGV7DmFV9kj9_P_BXyKTlFP_-qJN17TCGionjdJ45Hn6MbrkN_Vc2ZzuQC4P2e9mozFr2UeqnQWGfrIRBBBP5ttLsbgEEwnB7FpWpPvE9z4i_gc_XQ5zAcml0lh8?testcase_id=4591531706286080


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

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