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

Author: tkent
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/716c489b25ad9529994fc83be70b8c33b2f3b486
Time: Mon Feb 20 15:48:56 2017
Lines 276 of file DOMSelection.cpp which potentially caused crash are changed in this cl (frame #2, "chrome_child!blink::DOMSelection::collapseToEnd+0x92").
Minimum distance from crash line to modified line: 0. (file: DOMSelection.cpp, crashed on: 274, modified: 274).

ClusterFuzz has detected this issue as fixed in range 452175:452475.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: windows_syzyasan_chrome
Platform Id: windows

Crash Type: UNKNOWN
Crash Address: 0x0000003b
Crash State:
  blink::RangeBoundaryPoint::ensureOffsetIsValid
  blink::DOMSelection::collapseToEnd
  blink::V8Selection::collapseToEndMethodCallback
  
Memory Tool: SYZYASAN

Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_chrome&range=451616:451635
Fixed: https://clusterfuzz.com/revisions?job=windows_syzyasan_chrome&range=452175:452475

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94gqwGMEanCWekD-6ImaAlzYwEFU5RwnvjuQhp0Mm8CMwih3h-vFWeir_0k2y7z_xJ7MuYp4tTskiPUS1aEF-vmnEl9nWV-DA1bBXgLuvN6ERyXeoEUlWaSvvd6_FmXEls--yIlelWnGgdY2YQs5AsXzZScoJ56KWsjITCyvTpOhfiDsdKjRaCyJgwjxkQgK-_PkV40T7ovJemEYHw_reWi4Av1KOS_qDxSO8BUNpLda7RaOhphzWrXJiR8D15BvUBhZE8r9D11G_f6j5DyuRg7yTwxblaSkOuV5HD1YSOi2pwvoUxvFaFOZ0Jaa0sPLnonKiKy2WonVl0RckEINsTNONOZF9b7FduptRyFDciPbrxMws_M7flxGjS2xP86yeidapLIRrl4X5QB0aQkWQYm-0Ayxg?testcase_id=4609923930652672


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.

Maybe fixed by https://chromium.googlesource.com/chromium/src/+/136ec24ca9d6127754070a4ade5a904e6140bf16 .

BTW, I wonder why the crash fixed on Feb 23 was filed on Apr 18.