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/+/55d21e1555e7de5dd34e8ca115f27b3267870fee (Enable error page isolation.).

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.

I think it's in renderer/core/frame => Blink>Internals might be appropriate.

ClusterFuzz has detected this issue as fixed in range 586706:586707.

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

Fuzzer: puzzor
Job Type: linux_ubsan_vptr_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: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=570950:570951
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=586706:586707

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

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

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