Predator could not provide any possible suspects.
Assigning to concern owner from CL --
https://chromium.googlesource.com/chromium/src/+log/f88569b6a113509e7e7245ca297221701d07d4a3..b4bd8b431ace8883d071235502e716233e44d69f?pretty=fuller&n=10000

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/020397fbdf70bb4398dab310bccb437ba5b2377a

@tkent -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

My CL just replaced WebKit's RELEASE_ASSERT with CHECK.  It didn't have any logic changes.

Route to Editing triage.

Predator and CL could not provide any possible suspects.
Using the code search for the file, “CompositeEditCommand.cpp” assigning to concern owner from GIT revision log.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/9cee878cc63613dcd82f06850e5ab368b0bf8e57

@yosin -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

Thank You.

Mark Available to make someone picks this up.

Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/020397fbdf70bb4398dab310bccb437ba5b2377a (Replace RELEASE_ASSERT with CHECK in core/{dom,editing,html}).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

Sorry for the spam. Reassignments to previous owners won't keep happening.

ClusterFuzz has detected this issue as fixed in range 508976:508988.

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

Fuzzer: bj_broddelwerk
Job Type: windows_asan_content_shell
Platform Id: windows

Crash Type: Breakpoint
Crash Address: 0x717ea080
Crash State:
  blink::CreateMarkupAlgorithm<blink::EditingAlgorithm<blink::NodeTraversal>
  blink::CreateMarkup
  blink::CompositeEditCommand::MoveParagraphs
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=454203:454233
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_content_shell&range=508976:508988

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

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

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