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

Suspect CL: https://chromium.googlesource.com/chromium/src/+/8d9ab2bffbc57614331bc24edb50ff4b747238bd

peria@ -- Could you please look into this issue.

Thanks!

ClusterFuzz has detected this issue as fixed in range 578655:578656.

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

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=578655:578656

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

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

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

 Issue 892074  has been merged into this issue.

 Issue 894009  has been merged into this issue.

Reproducer doesn't reproduce this issue, even with the revision.
Archive this.