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

Author: sunyunjia
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/cb18694aff180e913277a346a37e74835935b37d
Time: Tue Aug 23 01:11:30 2016
Lines 323-344 of file SliderThumbElement.cpp which potentially caused crash are changed in this cl (frame #1, "blink::SliderContainerElement::handleTouchEvent"; frame #2, "blink::SliderContainerElement::defaultEventHandler").
Minimum distance from crash line to modified line: 0. (file: SliderThumbElement.cpp, crashed on: 321, modified: 321).

sunyunjia@, could you please take a look and help us to find correct owner if it is not related your changes.

ClusterFuzz has detected this issue as fixed in range 451526:451539.

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

Fuzzer: inferno_twister
Job Type: mac_asan_content_shell
Platform Id: mac

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  blink::HTMLFormControlElement::isDisabledOrReadOnly
  blink::SliderContainerElement::handleTouchEvent
  blink::SliderContainerElement::defaultEventHandler
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=mac_asan_content_shell&range=413548:413625
Fixed: https://cluster-fuzz.appspot.com/revisions?job=mac_asan_content_shell&range=451526:451539

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97gMJ3_FKedq5ZteUh0pakUw7nz5iL4nY6yKHAhSM6COhtCfVq73YcH7RZK8BEkVwYNeo6BFFdjE_ei678kPR-NZoharXBkbcTxI6fb1dclbaqzZlVTrkXL1xH5ctXHkcqGBH6Z5AkOFi0rkModvhU64DIbFX1XbOBC4Gnagch7mwCzYFT3hp3tQKOH617jQGZprHvXcXKCO9mUtWnzS7lCCUtG5EgDpBANxajKmSDAib7sYLj9S6dDXVbZPrgIanGFYKMb_OBJaGQY6Iq5LBbar8e9MCko3i_A4hZVfPpv1xYPPiBMC0E5XpFL4cxgI4Fyelz6_5fpZrhTPV5uO9nPYNmO0G9FyMWG9xXpwfcZFl0dbh3nx607yizZVKeixYWZo1V39CpN__m5INWl4vaDYQEPHg?testcase_id=5074090106028032


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

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