On Jul 26, 2011, at 7:34 AM, Kyle Sluder wrote:
On Jul 26, 2011, at 7:04 AM, James Merkel <jmerk...@mac.com> wrote:
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.
I don't see how this is unexpected behavior. You opened an image;
shouldn't the image be in memory?
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.
I'm pretty sure all image loading in the frameworks is done with
ImageIO. You're not going to escape it by using CGImage.
Can you explain more about why you think this is a problematic leak
and how it adversely affects you?
You might also try posting on quartz-dev.
--Kyle Sluder
I should have been more precise, namely: Every time an image is opened
and *closed*, the memory footprint increases by the size of the image.
For example, if a 27.5 MB image is opened and closed 10 times, you end
up with a memory footprint that has gown by 275 MB. The memory never
gets freed up.
This is a problem related to a CIImage memory leak and was discussed a
few years ago. Do a Google search or archives search with the terms
"CIImage memory leak" (without quotes).
Actually, I don't think the problem is in ImageIO -- I was just
referring to Instruments Object Allocations wherein if you click on
the offending GeneralBlock, Instruments says the "Responsible Library"
is ImageIO.
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
