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

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

Unable to find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label and requesting someone from dev team to look in to this issue.

ClusterFuzz has detected this issue as fixed in range 586874:586876.

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

Fuzzer: libFuzzer_minidump_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  reinterpret_cast<const MDCVInfoELF*>(&(*cv_record_)[0])-> cv_signature == MD_CVI
  google_breakpad::MinidumpModule::debug_file
  google_breakpad::MinidumpModule::debug_file
  
Sanitizer: address (ASAN)

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

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

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

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