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

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

ClusterFuzz has detected this issue as fixed in range 582171:582172.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  state_ == kDetached || !is_promise_called_ || !GetScriptState()->ContextIsValid(
  blink::ScriptPromiseResolver::~ScriptPromiseResolver
  blink::GarbageCollectedFinalized<blink::ScriptPromiseResolver>::FinalizeGarbageC
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=566155:566164
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=582171:582172

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

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

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