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

Suspect CL: https://chromium.googlesource.com/chromium/src/+/e51ec048e8a5b676f9ba02a8216bb5eedc7ce87c

yukishiino@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

My patch doesn't look related.  Blink>Editing>Command should be the best team to triage this issue.

ClusterFuzz has detected this issue as fixed in range 572927:572928.

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

Fuzzer: bj_broddelwerk
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !node_->parentNode(). LINK (editable) in append_node_command.cc
  blink::AppendNodeCommand::AppendNodeCommand
  blink::AppendNodeCommand::Create
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=572927:572928

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

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

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