Predator did not provide any possible suspects.
Assigning to concern owner from CL --
https://chromium.googlesource.com/chromium/src/+log/da2324ac7def06da46cbedba42084461af7db0f1..9e4e373603fa21b7099137642c74b82e0013f43d?pretty=fuller

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/70c3cc9eef1f7e1ed3c706095e3aaaaed5479c61

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

Track by 735774

ClusterFuzz has detected this issue as fixed in range 481254:481399.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: windows_asan_chrome_no_sandbox
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  start_ <= end_ (#text "\n\n"@offsetInAnchor[0] vs. Q id="htmlvarNUMBER" style="-
  blink::VisibleSelectionTemplate<blink::EditingAlgorithm<blink::NodeTraversal>
  blink::VisibleSelectionTemplate<blink::EditingAlgorithm<blink::NodeTraversal>
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=480591:480656
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=481254:481399

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.