You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
When opening http://docs.angularjs.org/ switching topics, Node Count according to TimeLine in Chrome DevTools growth upper and upper.
After approx. 50 sec quick clicking I got about 90000 nodes and 300mb.
As a site with documentation is heavily used not only by old developers, but also for newcomers, this issue can put AngularJS in not very attractive light....
(Based on http://stackoverflow.com/questions/19889702/is-this-a-memory-leak-of-angular)
When opening http://docs.angularjs.org/ switching topics, Node Count according to TimeLine in Chrome DevTools growth upper and upper.
After approx. 50 sec quick clicking I got about 90000 nodes and 300mb.
As a site with documentation is heavily used not only by old developers, but also for newcomers, this issue can put AngularJS in not very attractive light....
May be related with #2624
or https://code.google.com/p/v8/issues/detail?id=2073 or may be it is Disqus issue https://groups.google.com/forum/#!msg/disqus-dev/PFlJ68J--44/Qfqn_7uEOCsJ ?
Tested on Chrome 33.0.1705.0 canary, 30.0.1599.101
Hope this is not AngularJS issue but still think that it would be not bad to recheck once more.
The text was updated successfully, but these errors were encountered: