Re: Allocating too much memory kills my App rather than returning NULL
Re: Allocating too much memory kills my App rather than returning NULL
- Subject: Re: Allocating too much memory kills my App rather than returning NULL
- From: Don Quixote de la Mancha <email@hidden>
- Date: Tue, 08 Nov 2011 22:48:53 -0800
On Tue, Nov 8, 2011 at 10:39 PM, Conrad Shultz
<email@hidden> wrote:
> And there's a bigger problem. That memory warning notification that you
> referenced in your first message is there to tell you that you need to
> free up resources ASAP at run-time. Quoting from the iOS App
> Programming Guide:
>
> "Using large amounts of memory can seriously degrade system performance
> and potentially cause the system to terminate your app."
...
> You are expected to allocate as LITTLE memory as possible, make caches
> discardable, and play nicely with memory warnings.
That's just it. I DON'T receive any memory warnings. As far as I can
tell, neither does the system send my App a UNIX signal.
I would have no problem if I received either a Cocoa Touch memory
warning or a UNIX signal. In either of those events I would have no
problem freeing up as much memory as the system required.
As it is now, I have no way at all to warn my user that the game grid
they configured might be too big. Either they get a new grid of the
desired size, or the iOS terminates my App, thereby destroying all the
user's state.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
http://www.dulcineatech.com
email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden