Assigning to concern owner using Predator results --
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 340, 347 of file SliderThumbElement.cpp which potentially caused crash are changed in this cl (frame #0, "content_shell!blink::SliderContainerElement::HandleTouchEvent+0x12"; frame #1, "content_shell!blink::SliderContainerElement::DefaultEventHandler+0x1d").
Minimum distance from crash line to modified line: 0. (file: SliderThumbElement.cpp, crashed on: 337, modified: 337).

@sunyunjia -- 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 465765:465806.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_syzyasan_content_shell
Platform Id: windows

Crash Type: UNKNOWN
Crash Address: 0x00000003
Crash State:
  blink::SliderContainerElement::HandleTouchEvent
  blink::SliderContainerElement::DefaultEventHandler
  blink::EventDispatcher::DispatchEventPostProcess
  
Memory Tool: SYZYASAN

Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=413548:413625
Fixed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=465765:465806

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv96xGs5b3vi2vAs_jpYe_VhX1cpdIeHMP0XOvtW19TJo8WNjh7j7LKGr4AAb1nZUSNMop02IBK_-IP1j6R3UjGy3QDirE_YBJ1gnskyijBs7eBk3Qr5ni5C0WjXoF4QhJ2OaXc-acVQID77fnBPCSXG635E8h84EXiBhvrk_OHgbHqPTs8ZdLgkGrhUCNbwtn-RQTwvWKUJp3uMxq8gYK0nvfXBYxGfWejBKLjoxnWyFh2ESwHDvjtmPHdNyoVBu-Ct1dmYi7MECDLTU_Gjum0eRNJk6Xqfm-bOR12mHwcNNKb36DAG7wBHZ0CcQK46jabeTJJx3gngB4K8PdNhdU6hBRw4QnH8oq3eHfPxrCc56yqoN-04?testcase_id=5623737597820928


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

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