# Ionic 3.1.1 A memory usage disaster? What are we missing? **URL:** \ **Category:** ionic-v3\ **Created:** [May 9, 2017, 5:22am UTC](https://forum.ionicframework.com/t/ionic-3-1-1-a-memory-usage-disaster-what-are-we-missing/89458 "2017-05-09T05:22:36Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![disrupt](https://sea1.discourse-cdn.com/ionicframework/user_avatar/forum.ionicframework.com/disrupt/32/8233_2.png) [@disrupt](https://forum.ionicframework.com/u/disrupt)\ **Post date:** [May 9, 2017, 5:22am UTC](https://forum.ionicframework.com/t/ionic-3-1-1-a-memory-usage-disaster-what-are-we-missing/89458/1 "2017-05-09T05:22:36Z")
Guys … UGH … Please excuse the title … as i’d like to believe i am missing something here… but … In an attempt to eliminate memory leaks from our app, we have stripped our app down to absolute bare bones … and intend on re-implementing logic and complexity one step at a time all the while working to eliminate memory leaks… Simply put … We cannot even get past rending a page in its simplest form, with static content in the content area … and **scrolling leaks memory.** As i scroll a content area that contains a basic list of static content up or down while monitoring memory usage in xcode, i see the memory usage increase by approximately ~2.2mb each time i scroll, and this memory is never released. Should that be acceptable? Will Apple reject it just based on this alone? ```auto Cordova CLI: 6.5.0 Ionic Framework Version: 3.1.1 Ionic CLI Version: 2.2.3 Ionic App Lib Version: 2.2.1 Ionic App Scripts Version: 1.3.4 ios-deploy version: 1.9.1 ios-sim version: 5.0.13 OS: macOS Sierra Node Version: v7.9.0 Xcode version: Xcode 8.3 Build version 8W120l ``` I should add … currently we are using the WKWebView, but this problem is even worse using a UIWebView ---
**Author:** ![AaronSterling](https://avatars.discourse-cdn.com/v4/letter/a/51bf81/32.png) [@AaronSterling](https://forum.ionicframework.com/u/AaronSterling)\ **Post date:** [May 9, 2017, 5:56am UTC](https://forum.ionicframework.com/t/ionic-3-1-1-a-memory-usage-disaster-what-are-we-missing/89458/2 "2017-05-09T05:56:05Z")
I’ve followed your posts here with some interest, even though I have nothing to contribute, because I think you might have encountered a real issue that needs fixing. But could you clarify? Is this with pages lazy-loaded, after you permit the destruction of a page by popping it off the nav stack, the memory is never released? Or are you saying you could have an app with a single page component, and scroll up and down, and eventually you’d get an out of memory error after say 1000 swipes? Or are you saying something else? ---
**Author:** ![disrupt](https://sea1.discourse-cdn.com/ionicframework/user_avatar/forum.ionicframework.com/disrupt/32/8233_2.png) [@disrupt](https://forum.ionicframework.com/u/disrupt)\ **Post date:** [May 9, 2017, 6:07am UTC](https://forum.ionicframework.com/t/ionic-3-1-1-a-memory-usage-disaster-what-are-we-missing/89458/3 "2017-05-09T06:07:27Z")
Thank you for taking the time to respond … Currently, lazy loaded, although loading the page eagerly does not seem to matter. To answer your question - yes, it would seem that scrolling alone would eventually crash the app… i opened an issue with steps to reproduce… see my next comment … ---
**Author:** ![disrupt](https://sea1.discourse-cdn.com/ionicframework/user_avatar/forum.ionicframework.com/disrupt/32/8233_2.png) [@disrupt](https://forum.ionicframework.com/u/disrupt)\ **Post date:** [May 9, 2017, 8:03am UTC](https://forum.ionicframework.com/t/ionic-3-1-1-a-memory-usage-disaster-what-are-we-missing/89458/4 "2017-05-09T08:03:34Z")
See this issue i have opened up for reference: >