Skip to main content
S
Skrekkur3
Inspiring
May 14, 2013
Question

Memory warning reaction on iOS unacceptable

  • May 14, 2013
  • 1 reply
  • 1474 views

Hi.

I have an application on iOS iPad that performs ok until it reaches the point that iOS sends a lot of memory warnings and every time the AIR runtime re-acts with full garbage collection, that in turn leads to some Decompressing images, and the application crawls at 1.5 fps spending all the time garbage collecting and decompressing images.

The thing is that the client has some caches and stuff it could unload if only the application got some kind of event saying that it recieved memory warning (like you can do with native iOS code.

Also Im not entirely sure the AIR runtime is responding correctly.

Is there any way the application code can recieve this warning as well, and do some housekeeping?

And any idea why a garbage collection could cause "Decompressing images" is something getting collected that shouldn't (we are using plenty of embedded flash assets (via swc).

I am using the FLEX compiler with AIR 3.7

This topic has been closed for replies.

1 reply

chris.campbell
chris.campbell
Legend
May 16, 2013

Could you please open a new bug report on this over at bugbase.adobe.com?  When adding the bug, please include sample code or an application so we can quickly test this out internally.  If you'd like to keep this private, feel free to email the attachment to me directly (ccampbel@adobe.com). 

Once added, please post back with the URL so that others affected can add their comments and votes.

S
Skrekkur3Author
Inspiring
May 16, 2013

I guess this is more of a feature request. The ability to get some kind of memory warning on a mobile device when it gets it from the OS. This is standard practice in native iOS apps and I guess in android as well.

The bug is sort of when the application is almost out of memory and recieving constant memory warning from system. (verified through Xcode Organiser) the only response from the mobile Air app is to garbage collect.. and possibly some cached images/loaders, that can cause the image to re-decompress.

I guess I will it add it as a feature in bug-base.

chris.campbell
chris.campbell
Legend
May 16, 2013

Thanks, the bug base is the place for feature requests too.  Once added, definitely post back with the bug url and hopefully other like minded individuals will add their votes and comments.

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