Re: Memory leak in Apple's image handling frameworks ?
Re: Memory leak in Apple's image handling frameworks ?
- Subject: Re: Memory leak in Apple's image handling frameworks ?
- From: Gabriel Zachmann via Cocoa-dev <email@hidden>
- Date: Mon, 1 May 2023 12:08:33 +0200
Thanks a lot for your response!
I am not sure, though, I understand what you mean.
I've got 3 autoreleasepool's in different places in my source code. They are
just
@autoreleasepool { ... do something ... }
What do you mean by "insufficient use" ? and how do you mean "exit the nearest
autorelease pool block"? is there a problem if I do a 'return' inside an
@autoreleasepool { }
?
(And why should it be a problem whith just one out of 100k+ files? :-) )
Best regards, Gabriel
> On 1. May 2023, at 03:46, Christopher Snowhill <email@hidden> wrote:
>
> Another possibility is insufficient use of autorelease pools. Even if you are
> freeing your Objective C objects, if you do not exit the nearest autorelease
> pool block, they will simply accumulate in the heap. Leak tools will not
> consider these to be "leaked" memory.
>
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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