Memory leak with Ember 2.13 and partials
See original GitHub issueRendering the same partial multiple times keeps adding entries to a “glimmer-environment” cache (container.lookup('service:-glimmer-environment').constants) which is causing a memory leak.
eg. https://ember-twiddle.com/d6644950e2755c960c6cddbbe07d78b4
Click the “show/hide” button and notice that the value for glimmerEnv.constants.strings.length keeps going up.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
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 >ember-source | Yarn - Package Manager
Ember.js is a JavaScript framework that greatly reduces the time, effort and resources needed to build any web application. It is focused on...
Read more >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 >js.ember Changelog - pyup.io
2.13.0. - [15111](https://github.com/emberjs/ember.js/pull/15111) ... Fixes memory leak with attributes specified within quotes in the template (i.e. `<div ...
Read more >Source - GitHub
Ember Changelog ### v4.9.0-beta.4 (November 15, ... [#19820](https://github.com/emberjs/ember.js/pull/19820) Fix memory leak when ... 2.13.0 (April 27, ...
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

Thanks for reporting and including a nice reproduction!
FWIW, I did just test canary (which uses a pretty different architecture within glimmer and is slated to be in Ember 2.15), and this issue doesn’t exist there.
Closing this as it was fix for 2.15+ and current LTS is 2.16