On Nov 20, 2008, at 2:43 PM, Jean-Nicolas Jolivet wrote:
From what I can see... it seems like OS X (or BSD or whatever
manages that) will use a lot of memory if it has a lot of memory
available (I have 4gb)... and use less if it has less... I might be
wrong about that but it seems to be wo
Well, I posted my other msg before I saw your reply... but I guess
you're right, it would explain the unreliable results I am getting...
I'll trust Instrument on that one! :)
From what I can see... it seems like OS X (or BSD or whatever manages
that) will use a lot of memory if it has a lot
Just a quick update...
I ran Leaks (From the Instruments utility)... apparently the only
"leaks" I have are not related to images (some NSPathStore and strings
that I am not responsible for...those appear to be the only leaks)
So basically should I assume I am not doing anything wrong?
On Nov 20, 2008, at 2:10 PM, Jean-Nicolas Jolivet wrote:
However it seems like something is not getting released properly...
I'm looking at Activity Monitor and the memory usage is climbing
fast each time I click the preview button... (like 2-3mb each time)...
Is there a better way to do i
I'm using an NSImageView to preview an image result (i.e. you adjust
brightness etc.. then click preview and the image is displayed in the
NSImaveView)...
Basically everytime the image is previewed, a new NSImage object is
created... right now I'm using:
NSImage *displayPreviewImage = [[[
