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

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

Predator has provided 2 possible suspects

Suspect CL: https://chromium.googlesource.com/chromium/src/+/51ad2417ab848793ce9ca38666dc6c01e30be658

yuzus@  -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

Thank You.

I'm sure this CL will fix this issue. Waiting it to be merged.

https://chromium-review.googlesource.com/c/chromium/src/+/721681

ClusterFuzz has detected this issue as fixed in range 509545:509629.

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

Fuzzer: inferno_twister
Job Type: windows_syzyasan_content_shell
Platform Id: windows

Crash Type: Null-dereference
Crash Address: 0x00000523
Crash State:
  blink::IncrementLoadEventDelayCount::ClearAndCheckLoadEvent
  base::internal::Invoker<base::internal::BindState<void
  base::internal::Invoker<base::internal::BindState<void
  
Memory Tool: SYZYASAN

Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=508987:508992
Fixed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=509545:509629

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

Additional requirements: Requires HTTP

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

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