Re: "Live" image preview, huge memory usage...
Re: "Live" image preview, huge memory usage...
- Subject: Re: "Live" image preview, huge memory usage...
- From: Jean-Nicolas Jolivet <email@hidden>
- Date: Wed, 03 Dec 2008 02:34:05 -0500
Hmm I just found an older post that mentions a big memory leak problem
when drawing CIImage offscreen.... I guess I'll have to do this
differently...
On 3-Dec-08, at 2:20 AM, Jean-Nicolas Jolivet wrote:
hmmm while playing with Instruments and Activity Monitor I realized
two things...first, Activity Monitor (as I knew already) is not
really a good indication for finding leaks...
Also, It seems like the memory usage is climbing only when I make
usage of CIImage... if I only re-size/crop the picture, the memory
usage stays under 20mb... if I modify brightness or contrast 4-5
times (the only operations using CIImage), then Im up in the 170mb
of ram...
Does CoreImage really use that much memory? I'm pretty sure I can
get it up above 500mb pretty quickly.. this can't be right...
On 3-Dec-08, at 2:02 AM, Jean-Nicolas Jolivet wrote:
mmm thanks for the info, I'm trying right now to draw directly in a
custom view... unfortunately I still get the same result... on
average each time I regenerate the preview the memory usage in
Activity monitor goes up by approx. 10mb (real memory), and never
comes down... at this rate it climbs pretty quickly...
Once again, MallocDebug doesn't show any leaks, neither does
Instruments... not sure what I am doing wrong...
On 3-Dec-08, at 1:33 AM, Rob Keniger wrote:
On 03/12/2008, at 1:53 PM, Jean-Nicolas Jolivet wrote:
since I already have a bitmapImageRep I figured displaying its
data in an NSImaveView was probably not a big loss in terms of
performance... I wonder if drawing directly would be worth it in
my case... and most importantly, if it would help solve my huge
memory problem (perhaps drawing directly instead of storing the
preview in an imageRep would help on the memory usage though so
you might have a point!)
I'd definitely try drawing directly, in my experience NSImageView
does quite a few funky things (probably for caching/performance
reasons) and generally if you're changing the image a lot it's
best to just draw directly in your own custom view.
--
Rob Keniger
_______________________________________________
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
Jean-Nicolas Jolivet
email@hidden
http://www.silverscripting.com
_______________________________________________
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
Jean-Nicolas Jolivet
email@hidden
http://www.silverscripting.com
_______________________________________________
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
Jean-Nicolas Jolivet
email@hidden
http://www.silverscripting.com
_______________________________________________
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