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

Author: smcgruer
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/b693f94a81551da0334f9fb297813e617d9539c0
Time: Fri Feb 24 22:07:18 2017
Lines 1978 of file FrameView.cpp which potentially caused crash are changed in this cl (frame #2, "blink::FrameView::updateLayersAndCompositingAfterScrollIfNeeded").
Minimum distance from crash line to modified line: 0. (file: FrameView.cpp, crashed on: 1975, modified: 1975).

I'm unclear; was this clusterfuzz run before or after https://codereview.chromium.org/2720823002/ was submitted ? At first glance I suspect its the same crash as issue 696173 which that CL fixed.

ClusterFuzz has detected this issue as fixed in range 453593:453649.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4529059746021376

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000068
Crash State:
  get
  getScrollableArea
  blink::FrameView::updateLayersAndCompositingAfterScrollIfNeeded
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=452941:453056
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=453593:453649

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95kcykksy67APT-o7aVmxCFkNKKJOW8nkK8H-UsyBJ6yVkfu4dTMNpeN6V9auR-jhCAgwrAMMcXWY87eW1Yc6gNV0frVs59jNZw4kQFn-ZOfnkejp8TjeIWM2v2mJehubI_CosdBZnJBG8G_6r8zeNocTljANEv2-gxGWRNNsSFS9gWSHxNf2_FY-q_DnhLT-HST2YO1eUMvWrE_mDZa43L-XdgTgiAap2Rstu61AkhQrW3te6qAwmc3iPBqywdCxwM5R0gqomdVG1wqsWcUe7DosJwkND9ZWpoAnOgGsm0upDqhnxQHk4jEqN8wwnUoacRE8LLddeVIeKPIChhyCzOCb74lTB0un0XALg8pLwVypADzYQ?testcase_id=4529059746021376


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

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