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 was unable to identify any culprit changelists for this test case.

> From the above regression range, observing some changes related to spellcheck, so suspecting the same.

https://chromium.googlesource.com/chromium/src/+/8712023f7d10238966ed56d02d27f10e02c8c394

xiaochengh@ Could you please take a look in to this issue?

Thanks!

P3/Available as there is code after the DCHECK handling the null position case, so the DCHECK hit doesn't cause any user visible impact in production. And there's no minimized test case.

And editing has a lot of such gotchas that are hard to fix...

ClusterFuzz has detected this issue as fixed in range 571364:571366.

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

Fuzzer: bj_broddelwerk
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  visible_end.IsNotNull() in visible_units_sentence.cc
  blink::ExpandEndToSentenceBoundary
  blink::ColdModeSpellCheckRequester::RequestCheckingForNextChunk
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=552268:552270
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=571364:571366

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

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

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