Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.
Thank You.

Fix in change: https://chromium-review.googlesource.com/700419

ClusterFuzz testcase 4824388338974720 is still reproducing on tip-of-tree build (trunk).

Please re-test your fix against this testcase and if the fix was incorrect or incomplete, please re-open the bug. Otherwise, ignore this notification and add ClusterFuzz-Wrong label.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a79ff1d1787e61497996f9a6beed3557f26da1fd

commit a79ff1d1787e61497996f9a6beed3557f26da1fd
Author: Dave Tapuska <dtapuska@chromium.org>
Date: Wed Jan 03 18:17:49 2018

Don't crash browser on invalid input received from the injection channels.

Invalid input should be thrown out not cause a crash of the browser.

BUG= 772626 

Change-Id: I26128ff4491987cb6798f7f0f0078102c44dca43
Reviewed-on: https://chromium-review.googlesource.com/847305
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#526745}
[modify] https://crrev.com/a79ff1d1787e61497996f9a6beed3557f26da1fd/content/browser/renderer_host/input/synthetic_gesture_target_base.cc

ClusterFuzz has detected this issue as fixed in range 526714:526751.

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

Fuzzer: inferno_twister
Job Type: mac_asan_content_shell
Platform Id: mac

Crash Type: CHECK failure
Crash Address: 
Crash State:
  event.GetType() != WebInputEvent::kMouseDown || PointIsWithinContents(web_mouse.
  content::SyntheticGestureTargetBase::DispatchInputEventToPlatform
  content::SyntheticGestureTargetMac::DispatchInputEventToPlatform
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=441984:442831
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=526714:526751

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4824388338974720

See https://github.com/google/clusterfuzz-tools 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 4824388338974720 is verified as fixed, so closing issue as verified.

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