Assigning to the concern owner from 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 323-344 of file SliderThumbElement.cpp which potentially caused crash are changed in this cl (frame #0, "blink::SliderContainerElement::handleTouchEvent"; frame #1, "blink::SliderContainerElement::defaultEventHandler").
Minimum distance from crash line to modified line: 0. (file: SliderThumbElement.cpp, crashed on: 321, modified: 321).

@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 455091:455394.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_content_shell_drt
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=413548:413636
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=455091:455394

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv953MEFG_uPrnMZaWIAQnkxMgKy4ZAu8FQqtAO3WpIrKXxGuNBQLi_v-MxSG9-6SFtoA25bWwqrH1Aqos8-QaN_UJrF2KxeZ5sbS1mXF29FXXxLMgdIhG4EeWW8HWf4MLhT6nlItrGuMcpnM09o7U-ardmIYHY5qXGBKSm6HDCzN0TnjzAztpBVGN9KGv3dA9dMDJZjlmRo5La7QRNR0eC9eTPPmA9BfJ1QWfCihTyfDQ8h2C6COXVeiprywuA-EZSrIaA6Sd9bJzySzK4ooIY4rs8IDZpfOBTZkiwxEbXDzeBJlsBNSCYXjRnj8GcMUqwvT4Ujrn4zxgRj6a-GtFilbuecRHBKzBYjjckl4ajVR0_PaANg?testcase_id=5480454863192064


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

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