On Nov 10, 2011, at 9:33 AM, James Montgomerie wrote: > On 9 Nov 2011, at 17:33, Dave Camp wrote: >> This was discussed at a WWDC session a couple of years ago. If your app >> attempts to allocate a large block of memory, and the OS cannot get other >> processes to give up memory in a timely fashion, your app will be killed. >> >> It's the reverse of you getting the low memory messages. As you take up more >> and more memory, the OS has to send the low memory messages to other apps to >> get them to release memory for you. If you allocate memory faster than the >> OS can re-claim it from other processes, your app will be terminated. > > Maybe you didn't mean it this way, but this makes sound as if the foreground > app never gets memory warnings, it's just terminated if it uses too much RAM. > This is not true. In general, the opposite is true - other apps that have > been suspended are not 'woken up' just to be given warnings - they're just > terminated.
Your both right. The foreground application will receive memory warnings, but memory warnings are an event, just as much as touches are. What that means is that if your application is consuming memory slowly and returning to the event loop often, you will get memory warnings. But if your application is in a tight loop on the main thread forcing the allocation of lots of physical pages, then you can and will get killed without having "received" a memory warning. -- David Duncan _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
