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/+/0e114bd492826a638c43acd6d9e4c3d050d0671e (Support multiple touch pointers).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

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

sahel@, can you please look into it? seems like you've worked on similar issue (https://bugs.chromium.org/p/chromium/issues/detail?id=628525) before.

Thank you in advance!

https://chromium-review.googlesource.com/1113898 is the suspected cl which modifies some logic related to synthetic pointer/touch? events, and some changes in synthetic_web_input_event_builders.cc, Is it possible that the changes cause generation of synthetic GFSs with zero velocity?

lanwei@ please feel free to reassign it to me if you think the suspected change cannot be the cause of the issue.

ccing the reviewers of the suspected cl for more ideas.

Mass UI Triage.

ClusterFuzz has detected this issue as fixed in range 619628:619629.

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

Fuzzer: inferno_layout_test_fuzzer
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  max_start_velocity > 0 in fling_curve.cc
  ui::FlingCurve::FlingCurve
  CreateDefaultPlatformCurve
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=570828:570829
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=619628:619629

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 4671750428950528 is verified as fixed, so closing issue as verified.

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