Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/9984945dbe893379b16d01093c5cd30801ff782e (Scrolling with Mac mouse don't cause rubber banding.).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

I reproduced the crash, here is the main reason:
synthetic_gesture_target_base.cc(77)] Check failed: event.GetType() != WebInputEvent::kMouseDown || PointIsWithinContents(web_mouse.PositionInWidget().x, web_mouse.PositionInWidget().y). Mouse pointer is not within content bounds on MouseDown

The suspected cl (https://chromium-review.googlesource.com/779659) is not related to the crash and I could reproduce the crash after reverting the cl as well.

 nzolghadr@ are you aware of any related changes that might cause the issue?

We need to change the gpu benchmarking not to crash in these scenarios of bad input.

ClusterFuzz has detected this issue as fixed in range 526740:526745.

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

Fuzzer: inferno_twister
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900006f5c
Crash State:
  content::SyntheticGestureTargetBase::DispatchInputEventToPlatform
  content::SyntheticMouseDriver::DispatchEvent
  content::SyntheticPointerAction::ForwardTouchOrMouseInputEvents
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=518240:518474
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=526740:526745

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

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

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