Predator and CL could not provide any possible suspects.

Using Code Search for the file, "synthetic_gesture_target_base.cc" assigning to the concern owner who might be related.

Suspect CL: https://chromium.googlesource.com/chromium/src/+/ff30a0e48df5a0de78c693aa3c377d760a4dfdf7

mustaq@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

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

commit 1c9da9701d7063d51cc0d42cd3d1c05fbc251995
Author: Mustaq Ahmed <mustaq@google.com>
Date: Fri Jan 05 20:26:05 2018

Avoid browser crash when touch events are not supported.

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

ClusterFuzz has detected this issue as fixed in range 527339:527382.

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

Fuzzer: inferno_twister
Job Type: mac_asan_content_shell
Platform Id: mac

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false. Touch events not supported for this browser in synthetic_gesture_target_b
  content::SyntheticGestureTargetBase::DispatchWebTouchEventToPlatform
  content::SyntheticGestureTargetBase::DispatchInputEventToPlatform
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=434769:434830
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=527339:527382

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

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

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