Predator and CL did not provide any possible suspects.
Using Code Search for the file, "device_orientation_event_pump.cc" assigning to the concern owner.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/188eafdbbbb5bdc32823fb73944abccd2bbda5ed

@blundell -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Hi, that "Reproducer Testcase" link seems to just lead to a blank paper. Is there something that I'm missing?

ClusterFuzz has detected this issue as fixed in range 488838:488849.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_syzyasan_content_shell
Platform Id: windows

Crash Type: Null-dereference
Crash Address: 0x00000003
Crash State:
  content::DeviceOrientationEventPumpBase::SendFakeDataForTesting
  base::internal::Invoker<base::internal::BindState<void
  base::debug::TaskAnnotator::RunTask
  
Memory Tool: SYZYASAN

Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=483901:483905
Fixed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=488838:488849

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


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

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