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: Sandy McGuffog <email@hidden>
- Date: Thu, 10 Nov 2011 06:34:02 +0200
In my experience, and I'm the author of PhotoRaw, which uses LOTS of memory for raw image conversion, 128MB is very optimistic. 50-70 on e.g., an iPad 1 is more like it, and even then there will be occasional situations where you get terminated.
Sandy
On Nov 9, 2011, at 11:00 PM, David Duncan wrote:
> On Nov 8, 2011, at 10:51 PM, Don Quixote de la Mancha wrote:
>
>> It's user-configurable. If the user asks for too big a grid, I want to be able to tell them that there isn't enough memory, then suggest they try a smaller grid.
>
>
> In a naive implementation using 1 byte per cell and a full duplicate of state for advancement, you can support an 8192x8192 grid in 128MB of memory, which while high is supportable on all devices that support iOS 5. With various optimizations you can increase this size significantly of course.
>
> But at a completely practical level, is 8K x 8K not a big enough max grid size?
> --
> David Duncan
>
> _______________________________________________
>
> 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
_______________________________________________
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