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/+/5361078a2944c3b70c5092bebecbf042fb824fc0 (Implement Element.toggleAttribute).

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.

As per the  Issue 867522  owner, assigning this issue to @peria.
@peria -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thanks.

It seems hitting DCHECK, which is disabled on public use cases,
and I guess it's a kind of GC lifetime issue with a race condition.

Let me de-prioritize this and let's wait for unified GC.

ClusterFuzz has detected this issue as fixed in range 595418:595420.

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

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=570347:570348
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=595418:595420

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

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

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