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: Sun, 30 Apr 2023 17:41:28 +0200
Thanks a lot for your response!
And thanks a lot for your hints to 'leaks'.
I tried it, but I don't see any "ROOT CYCLE" in the output of 'leaks'.
(I see a bunch of ROOT LEAKS, but in total it's just 6 kB.)
Also, in the Debugger of Xcode, when i click on "Debug Memory Graph" icon, I
get lots of graphs, but none of them shows a cycle.
Same when I double-click the memgraph file: I can select all the memory graphs
that go through CGImage, but none of them contains a cycle (and most of them
don't originate in my code).
And, yes, I do release the images using CFRelease() - but, of course, still
thanks for the thought!
( I also switched on MallocStackLogging, but that did not provide more info on
potential causes for the massive leak, of course.)
Still stymied, Gab.
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