Re: Memory Full or not
Re: Memory Full or not
- Subject: Re: Memory Full or not
- From: Dustin Voss <email@hidden>
- Date: Thu, 24 Jul 2003 20:24:53 -0700
On Thursday, July 24, 2003, at 09:54 AM, Stefan Pantke wrote:
Am Donnerstag, 24.07.03 um 16:50 Uhr schrieb Michael Monscheuer:
Did someone ever found out what happens if sending an alloc and
memory *really is* full (no physical or virtual memory left)?
Does an Exception raise? Does [<class> alloc] returns nil?
Does application just ends? ;-)
I tried to find out and never could find anything about this case
(OK, it might seem to be a rare situation with small apps, but with
really BIG documents it might happen though.)
MiMo,
you should get a nil pointer.
But if memory is really short, then I expect OS X allready began
heavily swapping and
the system is (pracically speaking) no longer useable, since all other
parts
and apps are constantly allocating and releasing memory.
A Unix system which has no more memory, is practically dead.
Is there a way to get a low-memory warning? Like a notification or
call-back of some type? Or even a periodic check? I seem to remember a
way to do this is Classic, where it would call a function when memory
was low. This would let the app clear caches and the like to free up
memory.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.