New issue
Advanced search Search tips

Issue 824670 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Indirect-leak in blink::KeyframeEffectModelBase::EnsureKeyframeGroups

Project Member Reported by ClusterFuzz, Mar 22 2018

Issue description

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

Fuzzer: marty_html_twiddler
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Indirect-leak
Crash Address: 
Crash State:
  blink::KeyframeEffectModelBase::EnsureKeyframeGroups
  blink::KeyframeEffectModelBase::SnapshotAllCompositorKeyframes
  blink::CSSAnimations::SnapshotCompositorKeyframes
  
Sanitizer: address (ASAN)

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

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, Mar 22 2018

Components: Blink>Animation
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.
Cc: flackr@chromium.org
Cc: -flackr@chromium.org
Owner: flackr@chromium.org
Status: Assigned (was: Untriaged)

Comment 5 by flackr@chromium.org, Apr 25 2018

Owner: yigu@chromium.org
Project Member

Comment 6 by ClusterFuzz, May 22 2018

Status: WontFix (was: Assigned)
ClusterFuzz testcase 6013809299554304 is flaky and no longer crashes, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Project Member

Comment 7 by ClusterFuzz, May 22 2018

ClusterFuzz testcase 6013809299554304 is flaky and no longer crashes, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Project Member

Comment 8 by ClusterFuzz, May 22 2018

ClusterFuzz testcase 6013809299554304 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