Suspected CL could be
https://chromium.googlesource.com/chromium/src/+/fe075c81bffa961dfbc1bccc2e47501f45b88484%5E%21/chrome/browser/browser_process_impl.cc
Last updated by dgn @ weeks ago , please have a look and reassign if needed.

Thank you.

Thanks. Better trace: 

BrowserProcessImpl::OnKeepAliveStateChanged()
KeepAliveRegistry::OnKeepAliveStateChanged()
KeepAliveRegistry::Register()
Browser::RegisterKeepAlive()
BrowserList::AddBrowser()
Browser::Browser()
extensions::WindowsCreateFunction::RunSync()
ChromeSyncExtensionFunction::Run()
ExtensionFunction::RunWithValidation()

Merging into 623727, that has the same root cause.

ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5120375994449920

Fuzzer: meacer_extension_apis
Job Type: linux_asan_chrome_mp
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false in browser_process_impl.cc
  BrowserProcessImpl::OnKeepAliveStateChanged
  KeepAliveRegistry::OnKeepAliveStateChanged
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_mp&range=381909:382014

Minimized Testcase (5.37 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96ut8QRHR24UMIbbi95oWd_8XX7Ur9hdyzPFvcJirn1cH73db-8N56_luwTz9PuhXrGqUM6sbiu_jcrmO9W-GAa5SiqzBdfAVyuWP8YvTH9dYDZXKyycfUR2RSkFY3zczGTUl1Jcx_xjrPo5BmwJ_eU_QfYPg?testcase_id=5120375994449920

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.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot