On Jan 4, 2010, at 5:31 AM, Quincey Morris wrote: > On Jan 3, 2010, at 18:21, Ben Haller wrote: > >> Bill, I for one would like to hear a bit more about this. What has changed >> in SL? Why would it ever be possible to outrun the collector? If the limit >> of memory is being reached, can't it always just do an immediate, >> synchronous collection before the call to +alloc returns? I'd love to have >> a better understanding of what's going on under the hood here... > > I think this: > > http://lists.apple.com/archives/Cocoa-dev/2009/Jun//msg01586.html > > is the thread where b.bum threw some light on that issue. (But I didn't > reread the whole thing, so some of what I remember may be from a different > thread.)
Yes -- this message covers the high level issues related to doing an exhaustive blocking scan-and-collect when memory runs low or, more specifically, out. http://lists.apple.com/archives/Cocoa-dev/2009/Jun//msg01630.html b.bum _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
