Re: Unexpected behaviour with autorelease pool
Re: Unexpected behaviour with autorelease pool
- Subject: Re: Unexpected behaviour with autorelease pool
- From: Ken Thomases <email@hidden>
- Date: Sun, 14 Dec 2008 16:27:45 -0600
On Dec 14, 2008, at 4:17 PM, Filip van der Meeren wrote:
If your system doesn't crash/hangs before you can stop it, then you
will see that the app is consuming memory like the Americans are
consuming oil.
And according to me, my program respects the Memory Management
rules. So I say there is a bug.
Then you misunderstand. Nothing in the Memory Management rules will
protect you, your program, or the system against your program
consuming large amounts of RAM or VM.
They just prevent leaks. But not all memory consumption constitutes a
leak.
There are implications to delayed release (a.k.a. autorelease pools)
that apply even if you are following the rules. You are responsible
for understanding and dealing with those implications.
If you think there's a bug, please point to the contractual obligation
on the part of the frameworks which you feel isn't being honored.
Regards,
Ken
_______________________________________________
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