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, "page.cc" suspecting the below Cl might have caused this issue

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

keishi@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

ClusterFuzz has detected this issue as fixed in range 596889:609905.

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

Fuzzer: attekett_dom_fuzzer
Job Type: linux_cfi_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  main_frame_->IsAttached() in page.cc
  blink::Page::RequestBeginMainFrameNotExpected
  blink::scheduler::MainThreadSchedulerImpl::DispatchRequestBeginMainFrameNotExpec
  
Sanitizer: cfi (CFI)

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=583005:583014
Fixed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=596889:609905

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

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

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