Direct-leak in google_breakpad::MinidumpContext::Read |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5649546165878784 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 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5649546165878784 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Dec 3
Automatically adding ccs based on OWNERS file / target commit history. If this is incorrect, please add ClusterFuzz-Wrong label.
,
Dec 3
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 let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Dec 3Labels: Test-Predator-Auto-Components