StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Your app is crashing because Jetsam (a.k.a memorystatus), which is iOS's low memory condition handler, kills it (this is similar to Linux's OOM and Android's LowMemory Killer). What you are seeing is the memory snapshot. Allow me to explain:</p> <pre> Free pages: 958 - how much free physical memory (in multiples of 4K) Active pages: 2673 - how many pages in physical memory have recently been used Inactive pages: 2118 - how many pages in physical memory have NOT recently been used Throttled pages: 101092 - how many pages are subject to throttling (long story, irrelevant here) Purgeable pages: 0 - how many pages can be kicked out, on low memory condition Wired pages: 22186 - how many pages are resident locked, mostly for kernel purposes, or shared libraries </pre> <p>Your app has the unfortunate and dubious honor of having the most resident memory (by orders of magnitude, compared to others). So when the low memory condition occurs - some app wanting to <code>malloc()</code> a large chunk, and not enough free pages remain - Jetsam simply chooses the top memory and -- boom. <code>Kill -9</code>. Hence, no debug dump, etc. iOS has no swap, so there's no way to dump processes on the swap to clear up memory. The only way is out. Death.</p> <p>What you can do about it:</p> <p>Before Jetsam kills you, there is usually a low memory notification via an event, which the Obj-C runtime translated into the <code>-didReceiveMemoryWarning</code>. So handle it. From what you're describing, you might also want to release the <code>UIView</code>s. Those consume a LOT of memory.</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