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

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

tommycli: Could you take a look at this and see if you can figure out what's going on here? The code in question dates back to 2013 (https://crrev.com/14619015) and has a CHECK for an "impossible" condition. But maybe it overlooks some sequence of events or async update?

ClusterFuzz has detected this issue as fixed in range 614363:614364.

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

Fuzzer: mbarbella_webgl
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=614363:614364

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

Additional requirements: Requires Gestures

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

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