Re: Running out of memory when adding CGImageRef-to-NSImage frames to QTMovie in NSOperation subclass

2009-02-11 Thread Michael Hanna
A follow-up for posterity. I use [NSImage -addRepresentation:] instead of -TIFFRepresentation and made the object life cycle local. The result in Instruments was that the object allocation graph(all objects still living), drew like how the stock market has been recently(up and down, indicating obj

Re: Running out of memory when adding CGImageRef-to-NSImage frames to QTMovie in NSOperation subclass

2009-02-07 Thread Ken Ferry
Hi Michael, The information to diagnose your problem is not in this message. Instruments can show you backtraces of where individual objects were allocated, and where they were retained and released. Two things with this line, though. anImage = [[NSImage alloc] initWithData:[bitmapRep TIFFRepres

Running out of memory when adding CGImageRef-to-NSImage frames to QTMovie in NSOperation subclass

2009-02-07 Thread Michael Hanna
I have an NSOperation that opens a CGImageRef from a digital camera(large file). It creates a full-size TIFFRepresentation in RAM, then scales it down to a smaller CGContextRef. I create an NSImage out of this CGContextRef. This same NSOperation then adds it to a QTMovie with the -addImage:forDurat