Hi
I saw others posted related topics but without a solution:
Thanks for a fantastic project, we feel ionic is by far the best hybrid platform available. We have used the platform in our apps; however, cordova / ionic / angular stability issues challenges our ability to quickly deploy and scale apps. To be clear, it is more important for us to have a stable platform, than more features (e.g., Ionic Creator).
One serious issue we’ve encountered are DOM node and memory leaks. We have verified this using ionic beta10, beta11 and the latest nightly build …
opened 11:16PM - 09 Apr 14 UTC
closed 09:07PM - 05 Apr 16 UTC
It appears that changing state increases memory usage with every transition. Her… e's a simple example. Open your browser's memory profiler and click "Get Clicky".
http://codepen.io/perrygovier/pen/FJgBa
Pages with more stuff on it tend to increase the amount of memory that gets eaten with each transition. Note the number of nodes and listeners never decreases.
On my app that uses a few larger lists, the app can quickly get to 200mb after just a few mins of manual clicking back and forth. I have yet to crash the app due to memory pressure, but it seems more a matter of impatience than something that wouldn't happen with continued use.
I believe this is less an issue with Ionic and more to do with Angular's UI Router, but I thought I'd start here as it's where it popped up for me.
[BountySource discussion that appears related](https://www.bountysource.com/issues/1177595-docs-angularjs-org-dom-nodes-leaking)
We are at the final stage before releasing our enterprise application and we will appreciate your quick response.
