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

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

The stack trace looks similar to another issue (focus event being handled during layout and triggering the ScriptForbiddenScope check), so marking this one as duplicate.

ClusterFuzz has detected this issue as fixed in range 525745:525753.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900000001
Crash State:
  blink::BeforeCallEnteredCallback
  v8::CallDepthScope<true>::CallDepthScope
  v8::Object::SetPrototype
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=524911:524926
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=525745:525753

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

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.