Re: NSOperationQueue Memory Leak

Inside your for loop you are allocating 10,000 NSInvocationOperation objects without adding them to your autorelease pool. Adding [processor autorelease]; as the last line of the for loop killed memory leakage for me. Without it my real memory would jump 10 MB each time queueOperations: ran, with

Re: NSOperationQueue Memory Leak

On Wed, Aug 6, 2008 at 9:38 AM, Mike Simmons <[EMAIL PROTECTED]> wrote: > I have an audio application that processes numerous audio streams into > ten-second clips, compresses the clips, and saves them to disk. Naturally, I > wanted to move from single-threaded processing to multithreaded processin

Re: NSOperationQueue Memory Leak

emoryMgmt/MemoryMgmt.html Regards Shripada On 07-Aug-08, at 6:33 AM, [EMAIL PROTECTED] wrote: Message: 7 Date: Wed, 06 Aug 2008 08:38:09 -0500 From: Mike Simmons <[EMAIL PROTECTED]> Subject: NSOperationQueue Memory Leak To: Cocoa-dev@lists.apple.com Message-ID: <[EMAIL PROTECTED]> Con

Re: NSOperationQueue Memory Leak

On Aug 6, 2008, at 7:38 AM, Mike Simmons wrote: processor = [[NSInvocationOperation alloc] initWithTarget:self selector:@selector(sayHi:) object:nil]; Why aren't you releasing this object? Nick Zitzmann ___ Cocoa-de

NSOperationQueue Memory Leak

I have an audio application that processes numerous audio streams into ten-second clips, compresses the clips, and saves them to disk. Naturally, I wanted to move from single-threaded processing to multithreaded processing for the clip compression/writing. That was easily done using the NSO