New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 846397 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Direct-leak in BindRepeating<

Project Member Reported by ClusterFuzz, May 24 2018

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5017939145916416

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  BindRepeating<
  BindRepeating<
  blink::LocalFrameView::SetupRenderThrottling
  
Sanitizer: address (ASAN)

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

Issue filed automatically.

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

Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
 
Project Member

Comment 1 by ClusterFuzz, May 24 2018

Components: Blink>Internals>WTF Internals>Core
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.

Comment 2 by yutak@chromium.org, May 25 2018

Components: -Internals>Core -Blink>Internals>WTF Blink>Internals>Frames Blink>Internals
Labels: Test-Predator-Wrong-Components
Looks similar to  bug 843774  (for which the cause was not identified).
Cc: brajkumar@chromium.org
Labels: CF-NeedsTriage
Unable to find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label and requesting someone from blink team to look in to this issue.

Thanks!
Project Member

Comment 4 by ClusterFuzz, Jun 26 2018

Status: WontFix (was: Untriaged)
ClusterFuzz testcase 5017939145916416 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