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/+/6bc702ce4e6080adf5fff8e998e5138de88f1f7c ([EventTiming] Implement Event Timing API).

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.

ClusterFuzz has detected this issue as fixed in range 562125:562126.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x0000000004d0
Crash State:
  blink::WindowPerformance::AddEventTiming
  blink::EventTiming::DidDispatchEvent
  blink::EventDispatcher::Dispatch
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=556508:556511
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=562125:562126

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

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.