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 13:19:36 +0200
Hm, on closer inspection, maybe it did help.
At the moment, at least, the memory footprint of my app levels out at 3GB
(which would be OK).
In any case, thanks again so much to everybody who chimed in!
Best regards, Gabriel
> On 1. May 2023, at 12:43, Gabriel Zachmann <email@hidden> wrote:
>
> Thanks a lot for the hint!
> I tried it, but it did not change anything in the behavior of the app.
>
> Best regards, Gabriel
>
>
>> On 1. May 2023, at 09:54, Sandy McGuffog <email@hidden> wrote:
>>
>> Yet another possible issue is that Apple’s frameworks tend to like to hold
>> onto and reuse objects like CALayers. As a result they also hold onto the
>> contents for much longer than you might think. I would at least try
>> imgLayer.contents = nil as soon as you’re sure the layer won’t be displayed
>> again.
>>
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