Navigated to the detailed report and observed the information, "Crash stack might be flaky".
@manoranjan -- Could you please look into the issue and provide us feedback.
Thank You.

yoshiki@, could you please see if something is related to your change? I am seeing lot of code base has been touched by you. Please feel free to assign it to right owner in case if this is your's.

Thank you!

Adding stevenjb@ also who is familiar with this kind of stack ( crbug.com/317489 ).

Thank you!

I don't know what to make of this crash. It looks like somehow MagnificationManager::Shutdown is getting called without MagnificationManager::Initialize, which doesn't appear to be logically possible without some other major problem.

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

ClusterFuzz has detected this issue as fixed in range 434587:434591.

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

Fuzzer: meacer_chromebot_extensions
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  g_magnification_manager in magnification_manager.cc
  chromeos::MagnificationManager::Shutdown
  chromeos::ChromeBrowserMainPartsChromeos::PostMainMessageLoopRun
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=428077:428329
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=434587:434591

Minimized Testcase (28.27 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97UaSOKb-bxCv1t2UJ4nuuQISJXHZFRt_z8pFf8kG72ViEb3g-OE2tBvfqqsl81ovGMwB25NG-BVzlF7W0c1g3hgH-afAlnRIoz8Sf5KUSa9yxYkwcn7PaEpoCpo-gnlOSDTwBR0yKdmYX7natkrY4NVbcJ6YiGV5inG5YVakWJqGDvPS4?testcase_id=5089496132747264

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.

ClusterFuzz testcase is verified as fixed, closing issue.

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