Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

I went through the setup for similar bugs earlier and can take this. I see this is automatically P1; if it's really needed for the current milestone it's possible I won't make it for branch, and am happy to give it up.

ClusterFuzz has detected this issue as fixed in range 621155:621156.

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

Fuzzer: inferno_twister_c
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !result().empty() in omnibox_edit_model.cc
  OmniboxEditModel::GetInfoForCurrentText
  OmniboxEditModel::CurrentMatch
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_chromeos&range=605575:605578
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_chromeos&range=621155:621156

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

Additional requirements: Requires Gestures

Additional requirements: Requires HTTP

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

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

ClusterFuzz testcase 5668425866936320 is verified as fixed, so closing issue as verified.

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