Skip to main content
kaveri2
Known Participant
Aug 25, 2014 12:05 PM UTC
Question

Slows down and crashes on iOS

I'm sorry that I haven't debugged further. I hope you are aware of performance issues regarding AIR 15 beta on iOS. I'm using the 20th of August version. The app works fine on simulator (except visual artifacts on bitmaps) and on Android. On iOS it's reported to be very slow and crashes in a situation, which I can't think of being special.

Using GPU renderMode, timeline animations with plenty of bitmaps.

This topic is closed to new replies. Start a new post to keep the conversation going.

10 replies

kaveri2Author
Known Participant
Dec 17, 2014 11:58 AM UTC

Hi Govinda,

I'm getting back to this thread, because I noticed that there's a new AIR 16 beta, which doesn't any longer support the old compiler. I had critical issues with the new compiler during AIR 15 beta, which you were able to reproduce. Can you tell if these issues have now been fixed? I can't test the new AIR 16 beta, since I don't have a Mac, which I understood was a requirement.

Translate
marcanw
Inspiring
Dec 17, 2014 12:09 PM UTC

Hi kaveri2,

You can compile iOS on PC with the latest Air beta.

You just can't compile 64 bit.

Hope it helps.

Translate
kaveri2Author
Known Participant
Dec 17, 2014 1:17 PM UTC

Thanks, downloaded and confirmed the export release building is quick, even with "-useLegacyAOT yes". Initial tests seem to work fine, so maybe the issue has been fixed. Unfortunately I'm not testing with exactly same code anymore.

Translate
kaveri2Author
Known Participant
Sep 10, 2014 8:12 PM UTC

I know this is no longer beta, but just to let you know that official AIR 15 version fixed some issues, not all. The rest were got fixed with "-useLegacyAOT yes". So it has something to do with the packaging the app in a wrong way. The places where the app crashed the most used MovieClips on timeline.

Translate
Adobe Employee
Govind11519869
Adobe Employee
Sep 11, 2014 4:56 AM UTC

Hi,

Thanks for reporting the issue. Could you please send a sample app to govindag@adobe.com ?

Thanks

Govinda Gupta

Translate
kaveri2Author
Known Participant
Sep 11, 2014 6:15 AM UTC

Thanks for replying. Unfortunately our app is a monolith and the bug affects parts of it, which are difficult to separate. I can give you the undocumented project files or I can try to reproduce the bug in a test project. I believe the bug is somehow related to having multiple MovieClip subclass definitions on different SWC files, and instantiating them on timeline.

Translate
Colin Holgate
Colin Holgate
Inspiring
Aug 25, 2014 12:12 PM UTC

You cannot get away with GPU mode and a timeline animation where every frame is different. If you are animating symbols, where the symbol is the same one from frame to frame, then it should work. But if the scene is constantly changing, the GPU memory gets filled up quickly, and AIR is having to replace those textures with new ones.

If the area of the screen that is animating is small enough, and if you're just doing 24 fps, Direct mode can give good enough performance, without the GPU memory issues. Even then, iPad Retina may not perform well enough, but there's a way to exclude iPad 3 from the High quality mode, and then the performance is better.

Translate
kaveri2Author
Known Participant
Aug 25, 2014 12:18 PM UTC

The animations are quite optimized, so it's not that. Everything runs fine with AIR 14 or AIR 15 on Android, with old hardware. I try to dig deeper into this when I have more time.

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