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

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

ClusterFuzz has detected this issue as fixed in range 507129:507186.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  content::DeviceOrientationEventPumpBase::SendFakeDataForTesting
  blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue
  blink::scheduler::TaskQueueManager::DoWork
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=474722:474803
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=507129:507186

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

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.