[BUGFIX] Destroy proxy object in BelongsTo relation when no longer needed. #5554
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
_promiseProxy
object that is used by the belongsTo relationship is not destroyed when no longer needed.This
_promiseProxy
keeps a reference to the internalModel. This especially a problem if the record is deleted while the other side of the relationship is still alive.This results for us in a large memory leak: our application has a small set of long living records and during the lifetime it receives a large number of records (those records will be deleted after a while) that has a belongsTo reference to the records in the first set.
There is also a memory leak when proxies are destroyed when the proxied object is still alive. (reported as a separate issue in ember.js)