Predator, CL & Code Search could not provide any possible suspects.
Adding CF-NeedsTriage label for further inputs. could some one please look into the issue and update.
Thanks.

Here is the Change Log from the above CF report.

https://chromium.googlesource.com/chromium/src/+log/62234589a64896729acb4a53c874e775aefb3daf..b677a41a4e30b6bf68bc4cd2a9ec8876d5e2f7ea?pretty=fuller&n=10000

wfh@, can you please look into this change (https://chromium.googlesource.com/chromium/src/+/dee978f1ee27b272aeebdc75cecc1ed4f8148eb6) if possible?

Thank you!

ClusterFuzz has detected this issue as fixed in range 510445:510468.

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

Fuzzer: libFuzzer_minidump_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  !frame->module->code_file().empty()
  google_breakpad::PrintStackMachineReadable
  google_breakpad::PrintProcessStateMachineReadable
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=416025:416193
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=510445:510468

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md 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 5041198430683136 is verified as fixed, so closing issue as verified.

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