Predator and CL could not provide any possible suspects.

Using Code Search for the file, "app/content_main_runner_impl.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/6740d6248c24fdb1a591dad3aaaf312919e35fa5

hanxi@ -- Could you please look into this issue.

Thanks!

Do you know the regression range? My CL was landed on May 22, and it was two months ago.

ClusterFuzz has detected this issue as fixed in range 578946:578947.

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

Fuzzer: inferno_webbot
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: Ill
Crash Address: 0x7f102d59f6ca
Crash State:
  service_manager::Main
  content::ContentMain
  ChromeMain
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=578946:578947

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

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

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