Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Memory leak with Ember.ObjectProxy
See original GitHub issueFor example I use Ember.ObjectProxy to wrap model and then pass it into template for render. I don’t know all the properties of the model that this proxy has subscribed to. If I want to remove the proxy later, the model retains references to the proxy in listeners and it causes memory leak.
There is no way to unsubscribe all the listeners that trigger change on a given target. It would be very nice to have such functionality.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Do I have a memory leak? - EmberMap
Memory leaks are hard to track down in Ember applications. They often happen slowly over long periods of time, which means you need...
Read more >Memory leak issues after Ember Upgrade to 3.24.0
We are facing an issue on JS heap size grows substantially over time, indicating a memory leak after ember upgrade to 3.24.0, DOM...
Read more >Async Data and Autotracking in Ember Octane - Chris Krycho
Last week, I described the use of a load helper and associated AsyncData type to move away from Ember's ObjectProxy and PromiseProxyMixin ....
Read more >npm:validated-changeset - Skypack
This is because Changeset wraps an Object with Ember.ObjectProxy internally, and overrides Ember.Object.get to hide this implementation ...
Read more >ember component memory leak - Stack Overflow
It turns out there was a memory leak. But the Ember team have already resolved it, just not released the fix. V2.2.0-beta.1 contains...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thank you, @les2
@mixonic From what I see in the new twiddle is that heap is constantly growing, hence memory is still leaking.
I’m going to close, but we can keep chatting about it and other approaches here.
I will gladly reopen if there is a proposal to implement differently, or if It turns out I am mistaken.