New issue
Advanced search Search tips

Issue 865326 link

Starred by 1 user
Status: WontFix
Owner:
piman@chromium.org
Closed: Jul 20
Cc:
khushals...@chromium.org
dsinclair@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Indirect-leak in base::WaitableEvent::WaitableEvent

Project Member Reported by ClusterFuzz, Jul 19 
Detailed report: https://clusterfuzz.com/testcase?key=5747525114658816

Fuzzer: attekett_dom_fuzzer
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  base::WaitableEvent::WaitableEvent
  content::ChildProcess::ChildProcess
  content::GpuProcess::GpuProcess
  
Sanitizer: address (ASAN)

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
Project Member

Comment 1 by ClusterFuzz, Jul 19

Components: Internals>Core Internals>GPU>Internals
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 2 by ClusterFuzz, Jul 20

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

Comment 3 by khushals...@chromium.org, Jul 20

Cc: khushals...@chromium.org
Owner: piman@chromium.org
Status: Assigned (was: Untriaged)
Why is it complaining about a stack allocated WaitableEvent being leaked?

Comment 4 by piman@chromium.org, Jul 20

Status: WontFix (was: Assigned)
Wontfix given the reproducibility and given that at worst this is a leak of a singleton (but I also don't think we leak it).
►

Sign in to add a comment