Direct-leak in google_breakpad::MinidumpContext::Read |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5518704859938816 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=5518704859938816 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Sep 5
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Dec 1
ClusterFuzz testcase 5518704859938816 appears to be flaky, updating reproducibility label.
,
Dec 1
ClusterFuzz testcase 5518704859938816 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Sep 5Owner: lgrey@chromium.org
Status: Assigned (was: Untriaged)