New issue
Advanced search Search tips

Issue 880643 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Dec 1
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Direct-leak in google_breakpad::MinidumpContext::Read

Project Member Reported by ClusterFuzz, Sep 5

Issue description

Detailed 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.
 
Project Member

Comment 1 by ClusterFuzz, Sep 5

Labels: Test-Predator-Auto-Owner
Owner: lgrey@chromium.org
Status: Assigned (was: Untriaged)
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.
Project Member

Comment 2 by ClusterFuzz, Sep 5

Components: Internals>CrashReporting
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

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

Comment 3 by ClusterFuzz, Dec 1

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 5518704859938816 appears to be flaky, updating reproducibility label.
Project Member

Comment 4 by ClusterFuzz, Dec 1

Status: WontFix (was: Assigned)
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