Skip to main content
S
Sean72
Known Participant
February 26, 2019
Answered

Rules of thumb for AIR app memory issues on iOS?

  • February 26, 2019
  • 1 reply
  • 876 views

The app I am working with has run into memory issues on iOS, specifically the iPad  ("reason" : "vm-pageshortage").    Are there rules of thumb that might help me resolve this?  For example, how much memory is typically 'OK' for an iOS app, and when does it start to become a resource issue?  I am also using a Stage3D library. 

I have used Scout to do some analysis, but besides the vast amount of used memory being 'uncategorized' (200MB), I am not sure what to look for, or what to optimize first. As an example, one stage of the app profiled in Scout on the AIR iOS simulator shows overall allocation of 300MB and GPU allocation of 110MB.

This topic has been closed for replies.
Correct answer zwetan_uk

I wrote about it here
https://discuss.as3lang.org/t/memory-and-performance/242

see the list of learning materials

1 reply

Z
zwetan_ukCorrect answer
Inspiring
February 26, 2019

I wrote about it here
https://discuss.as3lang.org/t/memory-and-performance/242

see the list of learning materials

S
Sean72Author
Known Participant
February 27, 2019

Thank you, it looks like it will help and I'll have to go through it properly.  I am also going to set up a test on a newer iPad, since the one I was using is probably long in the tooth to represent the average user.

Z
zwetan_uk
Inspiring
February 28, 2019

Newer device is nice to have but I would say keeping around an older device is even better for testing

eg. if it works "fast enough" on the older device it should works as good or better on newer device

and if you don't have enough device to test around
you can reach out to online services like
https://www.diawi.com/

or

How it works - Beta Family

etc.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices