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

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

Unable to find actual suspect through code search and also observing no possible suspect CL under regression range, hence adding appropriate label and requesting someone from internals team to look in to this issue.

Thanks!

 Issue 840632  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 557190:557192.

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

Fuzzer: mbarbella_js_mutation_layout
Job Type: linux_ubsan_vptr_content_shell_drt
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false. This function cannot be called if the main frame is not a local frame in 
  test_runner::WorkItemNonLoadingScript::Run
  test_runner::TestRunner::WorkQueue::ProcessWork
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=555986:555990
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=557190:557192

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

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

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