Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/d7ebcbcf5f4b8eeec191a1bb8e68d3b67f6d3b8d (Explicitly add signature and header in minidump fuzzer).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

Mark, is this anything to worry about? 

Leaks are always bad, but given https://clusterfuzz.com/download?testcase_id=5185524460683264, I can’t find a path in to MinidumpThread::GetContext at all, so I don’t know what to do here.

I did prepend the header from https://chromium.googlesource.com/chromium/src/+/d7ebcbcf5f4b8eeec191a1bb8e68d3b67f6d3b8d%5E%21/#F1.

ClusterFuzz has detected this issue as fixed in range 584316:584317.

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

Fuzzer: libFuzzer_minidump_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  google_breakpad::MinidumpContext::Read
  google_breakpad::MinidumpThread::GetContext
  google_breakpad::MinidumpProcessor::Process
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=510446:510468
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=584316:584317

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

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

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