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 and CL could not provide any possible suspects.

Using Code Search for the file, "frame_scheduler_impl.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/e2d89968d57604c3121004103f8aaf6e442dd5a1

shaseley@ -- Could you please look into this issue.

Thanks!

ClusterFuzz has detected this issue as fixed in range 576654:576655.

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

Fuzzer: phoglund_webrtc_peerconnection
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: Ill
Crash Address: 0x7f21a5a206ca
Crash State:
  blink::scheduler::FrameSchedulerImpl::InitializeTaskTypeQueueTraitsMap
  blink::scheduler::MainThreadSchedulerImpl::SchedulingSettings::SchedulingSetting
  blink::scheduler::MainThreadSchedulerImpl::MainThreadSchedulerImpl
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=576630:576633
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=576654:576655

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

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

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