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

Hi Mike processor = [[NSInvocationOperation alloc] initWithTarget:self selector:@selector(sayHi:) object:nil]; You are not releasing the operation objects you create!. You should have released them soon after they were added to the queue. -- [operationQueue addOperation:proce

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