Findit did not show any suspected CL's

Using code search suspecting the below change could be a possible culprit which could have resulted this crash.

Change URL: https://chromium.googlesource.com/chromium/src/+/4a975194104af57c2c05f8dc0144e94a79dc2076
Review-Url: https://codereview.chromium.org/2240983003

@ chongz: Assigning to you, Request you to please take a look into it. Please help us to reassign if not with respect to your change.

Thanks.!

My change is just moving the location of two class.

Suspect this issue to be high-DPI related, similar to  issue 638412  and  issue 638413 .

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

ClusterFuzz has detected this issue as fixed in range 454873:455052.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6250149938724864

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  PointIsWithinContents(web_wheel.x, web_wheel.y). Mouse wheel position is not wit
  content::SyntheticGestureTargetBase::DispatchInputEventToPlatform
  content::SyntheticSmoothMoveGesture::ForwardMouseWheelEvent
  
Sanitizer: undefined (UBSAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=398598:398917
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=454873:455052

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv953dlGvnBNcCFQ6z9BpvmTpBTSSf7_92iNtiXEipo2BPhN2ttmw6Z32xOC9n582fjq99-WJ7K3GcIrONEFzDgGt3K2ekQWb7hgaFF_3wV8NtaZOZ5QJCZGaqBsWQ9R_zcsLlINAFT3ATjNNUngbF_r4yrTOnw?testcase_id=6250149938724864


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.