New issue
Advanced search Search tips

Issue 866872 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

[Performance tab] nodes leaking on focus

Reported by bmsd...@gmail.com, Jul 24

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
1. goto: https://codepen.io/bmsdave/pen/ajWaKX (or download https://bmsdave.github.io/bugs/nodes_leaking_on_focus.html and try it local)
2. open DevTools (Preformance tab)
3. Collect garbage
4. Start Record
5. Click button "Click me"
6. wait 2 second
7. Collect garbage
8. Stop Record

What is the expected behavior?
Count of nodes after click "Click me" = count of nodes before click

What went wrong?
Count of nodes after click "Click me" != count of nodes before click

Did this work before? N/A 

Chrome version: 67.0.3396.99  Channel: stable
OS Version: 
Flash Version: 

performance tab: https://bmsdave.github.io/bugs/performance_tab.jpeg
dump: https://bmsdave.github.io/bugs/perf.json

memory tab: https://bmsdave.github.io/bugs/memory_tab.jpeg
dump:
https://bmsdave.github.io/bugs/before_click.heapsnapshot
https://bmsdave.github.io/bugs/after_click.heapsnapshot

Initially, the problem was discussed in this thread: https://github.com/angular/angular.js/issues/15588
 
Owner: alph@chromium.org
Status: Assigned (was: Unconfirmed)
It looks like fixed in Canary.
@alph, do we instrument node allocations for memory allocation timeline profiler?
If I remove ".remove()" from code snippet I can see leaked nodes on timeline but I can not get allocation stack for them and got something like this object as allocated before profiler was started. Is it expected behavior?

Sign in to add a comment