Edit AllPages

I have a written a program that displays images in a CustomView using Core Image. I added two CIFilters to it, and it started leaking memory. I believe this is because I am retaining the filters, and not releasing them. However when I try to release both filters and the image, my program crashes. The relevant code from my CustomView follows:

Interestingly, I can release any one of the objects in my dealloc method, but if I try to do two or more, it crashes. Can someone straighten out my memory management?

Not without you telling us what line fails. Seriously, you can’t expect help by saying ‘one of the objects’. Tell us exactly what line crashes. You can use the debugger to do so. Set a breakpoint in your dealloc method and step through. Tell us what error you receive (just to make sure).

I literally meant “any” of the objects, if I do more than one, not just one in general. Nevertheless, when running the code above, here’s some more info: The error I get is: Program received signal: “EXC_BAD_ACCESS” It comes from the line [contrastFilter release]. However as I mentioned, if I release the contrastFilter first, it is fine, but then the sharpenFilter will crash when I release it. The same goes for the originalImage, if it is released first it is fine, but if it is second in line, it will crash. Here is the relevant stack trace:

#0 0xfffeff20 in objc_msgSend_rtp #1 0x9285f708 in NSPopAutoreleasePool #2 0x9422abac in -[CIFilter dealloc] #3 0x0003f7c4 in -[MyCIView dealloc] at MyCIView.m:69

Please post all the relevant code for “MyCIView” … the initialization routine and any routines that use the three ivars referenced above.

You have a memory leak in the first line of setImage:. Your are setting originalImage without releasing originalImage if it has already been set from a previous call to this method. –zootobbalu

Well that’s certainly *a problem, but not the problem. :-)*

I am only ever calling that method once, but I will update that in the future.

Here’s the class in it’s entirety:

#import “MyCIView.h” #import <Foundation/NSDictionary.h>

enum { MCContrast, MCSharpen };

@implementation MyCIView



In practice you should set your ivars (such as the filter, image, etc.) to nil in your initialization routine.

This is not true in ObjectiveC. The runtime sets (and is documented to set) all of your instance variables to 0/nil/NULL/0.0 when your object is created.

I have solved my own problem. The argument I was passing into the setImage method was being autoreleased in the previous method. So once it got into setImage, it’s retain count would have already been decremented by the autorelease. The retain call within setImage then sets the retainCount to 1 and finally when my method called release on it, the retainCount dropped to 0 and it released it not only in MyCIView, but in the previous method as well. Then when something else attempts to access it, it would crash. Or at least that’s how I believe it occurred.