On Jul 26, 2011, at 1:39 AM, Mike Abdullah wrote:
On 26 Jul 2011, at 01:55, James Merkel wrote:
Well, I see I have a huge memory leak in CIImage.
However, I don't see where my code is in error.
Also, according to Instruments Object Allocation, ImageIO is
holding this memory.
So I guess Core Image calls IImageIO.
Yes, since ImageIO's job is to read and write images, Core Image
uses it to do that portion of its work.
Yeah, it looks like I can't use CIImage because of the memory leak.
Every time an image is opened, the memory footprint increases by the
size of the image.
Using CIImage was kind of a cul-de-sac.
So now it looks like I have to use CGImage and figure out how to get a
CGImageRef into an NSImageView which is ultimately how the image is
displayed.
Jim Merkel
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
