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

Suspect CL: https://chromium.googlesource.com/chromium/src/+/099eef98bfd425d0ca08d5927831a242120c0b51

Since zhuoyu.qian@ is not a chromium member, assigning it to reviewer.

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

Thanks!

ClusterFuzz has detected this issue as fixed in range 577075:577076.

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

Fuzzer: bj_broddelwerk
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  selection.IsRange() in insert_list_command.cc
  blink::InsertListCommand::DoApply
  blink::CompositeEditCommand::Apply
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=576408:576410
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=577075:577076

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

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

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