I would assume you first have to ask yourself, which devices do you want your app to support? Xcode version: Xcode 8.3 Build version 8W120l I’d LOVE for someone to tell me what i might be doing wrong …īut separate from this simple example … Our app is much more complex … and the memory usage is ENORMOUS … We have followed all conventions with regard to unsubscribing to observables where necessary, nulling out Arrays and properties where necessary … Honestly, it all just seems completely un-realistic to try and deploy an Ionic / Angular app into the real world with problems like this … i dunno … we are just VERY discouraged by all of this … and its not like we can really ask Ionic for help directly… they have enough on their hands … never mind memory leaks. So with that i ask … and with all due respect … what good is Ionic if this is the case? If something that simple adds to Memory usage thats never released … eventually the app WILL crash.
We release the audio instance on exiting among other things in there … JUST SWITCHING TABS back and forth ADDS to the Memory usage … approximately ~4MB with each time this second tab instantiates … Now… NEVER MIND actually triggering those events, startRecord, Play etc …
catch(err => console.log('create file error:', err)) then(res => console.log('remove:', res)) catch(e => console.log('Error opening media file', e)) The second tab, when selected, fires ionViewDidEnter() which instantiates the File and Media plugins: import ).then(file => dioInstanceRecord = file) Our app instantiates and loads a tabs page that has 2 tabs. In addition to the plugins Ionic installs by default, StatusBar and Splashscreen, we additionally installed the Media and File plugins. We have slowly been stripping out functionality in our app to try to target whatever is causing the memory leaks… and are now down to a pretty bare bones app …
#CODELINK V2 LOCATION OF MEMORY BAR PLUGIN HOW TO#
Has ANYONE run into this problem or have ANY advice on how to avoid these memory issues? We are digging into the plugins to see if we can troubleshoot these issues, but thats an enormous undertaking … Apple’s tools do not really provide a way of tracking memory usage inside of a Cordova app. Something as simple as recording a 5 second audio clip via the MediaPlugin and then deleting it and releasing the instance does NOT clear memory.
Use a native feature like File or MediaPlugin and Memory usage grows with every instance by ENORMOUS amounts, DESPITE releasing instances after use. Where this problem REALLY shines is within any app that makes use of Native features. The most basic app alone, generated by the CLI using the Tabs template and then adding a simple form to one or more of those pages within it presents an ever increasing amount of Memory usage on iOS (safari UIWebView, WKWebView) when switching from one page to another … albeit, small increases … technically the app would crash eventually … but more importantly … APPLE will NOT allow an app that leaks memory in the app store. We have been testing several iterations of ionic apps.
What was not obvious to us? - all the problems as it relates to memory usage (leaks) on iOS. First, let me just say, we LOVE ionic … its amazing for all the obvious reasons…
0 kommentar(er)
