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 was archived by the owner on Apr 12, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
AngularJS: Memory Leak with ng-repeat using custom objects (w/simple PLUNKR) #11169
There is a leak using ng-repeat after the 2nd wave iterating over an array of custom objects like this :
<div ng-repeat="d_sampleObject in mySampleObjects">
{{d_sampleObject.description}}
</div>
NOTE: 'mySampleObjects' is an array of the following object instances:
ml.MySampleObject = function (id) {
this.id = id;
this.description = 'this is object #:' + ' '+id;
}
Memory profile reveals an extra 'd_sampleObject' left over and not de-referenced. More details (via a controller and an injected service) in the Stackoverflow link above. A simple demonstration also in the provided plunkr link. Any thoughts and help greatly appreciated in advance!
Reading the latest comments, is it safe to assume that this is indeed a bug in the framework? if so, what timeline should we expect to have a fix? Thanks for your efforts! @Narretz
I'd see this more of a limitation of the V8 garbage collector than a bug in Angular. It is however a nice little optimisation opportunity. If there are no issues the change will probably be part of 1.3.15.
Activity
perf(rootScope): Fix a memory leak
momoadeli commentedon Feb 25, 2015
Reading the latest comments, is it safe to assume that this is indeed a bug in the framework? if so, what timeline should we expect to have a fix? Thanks for your efforts! @Narretz
perf(rootScope): Fix a memory leak
realityking commentedon Feb 25, 2015
I'd see this more of a limitation of the V8 garbage collector than a bug in Angular. It is however a nice little optimisation opportunity. If there are no issues the change will probably be part of 1.3.15.
perf(rootScope): Fix a memory leak
fix(rootScope): prevent memory leak when destroying scopes
fix(rootScope): prevent memory leak when destroying scopes
fix(rootScope): prevent memory leak when destroying scopes
fix(rootScope): prevent memory leak when destroying scopes