Re: Garbage Collection: memory limits, crash when using "lots" of memory, why?
Re: Garbage Collection: memory limits, crash when using "lots" of memory, why?
- Subject: Re: Garbage Collection: memory limits, crash when using "lots" of memory, why?
- From: Sean McBride <email@hidden>
- Date: Fri, 23 Sep 2011 09:51:06 -0400
- Organization: Rogue Research Inc.
On Thu, 22 Sep 2011 22:33:49 -0700, Joar Wingfors said:
>> Exceeding the available memory of the garbage collector should not
>crash, instead your allocations should fail.
>
>When memory allocations fail, apps crash. Like it or not, that's just
>the way it is. Not sure what the alternative would be - Changing all (!)
>of our code to handle out-of-memory errors at every method / function
>call? And then if you were to catch such an error, having to handle it
>without being able to allocate memory?
Though in my case, I don't think that I'm 'out of memory'. To recap, I have 32 GB of physical RAM, gobs of virtual memory/disk space, a 64 bit process, and when I reach 4 GB used, NSMutableData crashes trying to do a mutableCopy. In what way is this 'out of memory'? And this only happens in GC, not MRC.
In any case, I've filed rdar://10169190
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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