StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I think your app crashes because of a memory issue</p> <p>To confirm that it's a memory issue, sync your device with iTunes,and look in <code>~/Library/Logs/CrashReporter/MobileDevice/</code> for a files with <code>LowMemory</code> in their name. If you see <code>(jettisoned)</code> next to your app name, that confirms it was killed by iOS for using too much memory.</p> <p>The only other way an app could exit without leaving a crash report is if it <a href="http://developer.apple.com/library/ios/qa/qa1561/" rel="nofollow">erroneously called <code>exit()</code></a>. </p> <p>For more information, see "<a href="https://developer.apple.com/library/ios/qa/qa1747/" rel="nofollow">Debugging Deployed iOS Apps</a>", and "<a href="https://developer.apple.com/library/ios/technotes/tn2151/" rel="nofollow">Understanding and Analyzing iOS Application Crash Reports</a>".</p> <p><strong>EDIT</strong></p> <p>what does <strong>jettisoned</strong> means?</p> <p>It means the process was terminated because iOS needed memory:</p> <blockquote> <p>Memory usage of each process is reported in terms of number of memory pages, which as of this writing are 4KB each. <em>You will see "(jettisoned)" next to the name of any process terminated by iOS to free up memory</em>. If you see it next to your application's name, that confirms the application was terminated for using too much memory.</p> <p><a href="http://developer.apple.com/library/ios/#technotes/tn2151/_index.html" rel="nofollow">Documentation</a></p> </blockquote> <p>I would take a look at that technical note for some additional help. The documentation also points out the Instruments does not measure graphics memory use, and that requires special handling.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload