Direct-leak in google_breakpad::MinidumpContext::Read |
||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5782251931697152 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 Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97eLliMJ7aXdj4KPyhBspDlsOazWxDXruYEQYxIwasDr9mUz_4MX8a1xpxo3T4GFoFTVSZmAOSGstCShE-F-w9ipmR0F-3uXVQZf2kzXOuIDGvKndRtMqxq5UqT68HBI-cgs0H2rh-hN3VFsb2RvtYyemLB629RotV08wELwfzV2T6p7-w?testcase_id=5782251931697152 Issue manually filed by: wfh See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Sep 7 2016
,
Nov 3 2016
kcc@ could you please look into this.please feel free to re-assigned back if needed. thanks in advance !
,
Nov 3 2016
mmohammad, why do you assign these bugs to me? I develop libFuzzer, the tool that finds these bugs, and I don't know the code where the bug is.
,
Nov 3 2016
assigning to Mark, as he looked at these in the past :) If not, I'll take a look next week.
,
Nov 4 2016
I’m going to be getting stricter about my “no junky Breakpad bugs” policy, because otherwise I’ll never be able to make progress on replacing it. I’ll still offer free consultation and therapy.
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 22 2016
ClusterFuzz testcase 5782251931697152 is flaky and no longer reproduces, 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 wfh@chromium.org
, Sep 2 2016