New issue
Advanced search Search tips

Issue 816105 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Direct-leak in Create

Project Member Reported by ClusterFuzz, Feb 24 2018

Issue description

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

Fuzzer: mbarbella_js_mutation_layout
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  Create
  blink::DocumentTimeline::DocumentTimeline
  blink::DocumentTimeline::Create
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_lsan_chrome_mp&range=539011:539012

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Feb 24 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.
Project Member

Comment 2 by ClusterFuzz, Feb 24 2018

Labels: Test-Predator-Auto-Owner
Owner: hidehiko@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/3aa61df502c16c7231afb2bcef4e94ff30a16b0b (Mark noexcept for Optional to catch up with C++17 spec.).

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.
Owner: ----
Status: Untriaged (was: Assigned)
According to stack trace, it fails in new(), which is unrelated to the CL. Unassigned myself.
Owner: flackr@chromium.org
It looks like a compoistorTimeline leaking to me.  By process, over to the TL
Status: Assigned (was: Untriaged)
Labels: Performance-Memory
Project Member

Comment 7 by ClusterFuzz, Mar 14 2018

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