On Jul 4, 2008, at 9:32 AM, Joan Lluch (casa) wrote:
However, this is hardly possible with GC even if you trigger the GC
manually in the middle of the loop. It simply will not release the
memory at the rate you expect because it follows its own rules and
as far as free memory is available it will not free anything unless
it is a reason, according to its algorithms, to do so.
This situation should work. If it does not, that's something to
report to Apple via the bug reporter http://bugreport.apple.com/ and,
if possible attach a test case that demonstrates the issue.
Do not assume that it's simply the collector "follow[ing] its own
rules." The collector should -- and DOES -- collect objects that it
can tell are no longer referenced. In fact, we've had occasional
threads here about objects used at the beginning of a method being
collected while interior pointers that they've handed out are still in
use, so it's not just hypothetical.
-- Chris
_______________________________________________
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
