Skip navigation
Currently Being Moderated

iOS application dies - suspect a memory issue

Jul 18, 2012 9:01 AM

Tags: #air #adobe #ios



I have a reasonably large AIR application developed in CS6 using AIR 3.3 (I tried 3.2 as well). Works fine on my computer but when I upload it to an iPhone the application tries to start but then dies and returns to the apple home screen.


The application contains about 12 screens each of which contain many (50+) variables / movie clips etc. Tried to debug it using the external debugger but no errors appear in CS6. When I limit the number of screens I create to e.g. 9 screens only it starts to work again. Which 3 I disable is totally irrelevant (first  or last 3 screens) - when I get down to 9 screens all is well.


I don't really know where to start looking for a solution to this. Anyone has any suggestions?





  • Currently Being Moderated
    Jul 18, 2012 9:41 AM   in reply to Doubledutch20

    Does closing all the background apps make any difference?

    Mark as:
  • Currently Being Moderated
    Jul 18, 2012 4:08 PM   in reply to Doubledutch20

    Using any ANEs? The number of slides could be a red herring.


    Have you looked at the Console pane in the iPhone Config Utility while running the app?

    Mark as:
  • Currently Being Moderated
    Jul 18, 2012 5:21 PM   in reply to random(1)

    9 or less works, 10 or more does not... show us your code.


    it could be a problem with a number of things, but is probably an easy fix:


    [for loops, naming conventions, missing objects, declaration of an object, etc...]

    Mark as:
  • Currently Being Moderated
    Jul 19, 2012 6:16 AM   in reply to Doubledutch20

    Doubledutch20 wrote:


    • "Using ANE's?": yes about 7 of them....

    Yikes. Based on my experience with native extensions, at least one of those ANEs is almost certainly the cause of the crash-on-startup problem.


    Take a look at the iTunes' CrashReporter folder on your Mac or PC. Most of the information in crash logs is not helpful, but you might get a better idea of what's causing the crashes.


    As for sending trace statements to the the Console pane -- it would probably require another ANE. I would stick to publishing for device debugging. By adding breakpoints and trace statements to your startup code, you should eventually find the code that's causing the crashes.

    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points