NSCoding leak problem with initWithCoder

Question

I have a leak in the following code:

-(id)initWithCoder:(NSCoder *)aDecoder {
    if (self = [super init]) {
        self.Tag = [aDecoder decodeObjectForKey:KEY_TAG];
        self.ParentTag = [aDecoder decodeObjectForKey:KEY_PARENT_TAG];
        self.Order = [aDecoder decodeObjectForKey:KEY_ORDER];
        self.OrderFavorite = [aDecoder decodeObjectForKey:KEY_ORDER_FAVORITE];
        self.isFavorite = [aDecoder decodeObjectForKey:KEY_IS_FAVORITE];
        self.isPurchased = [aDecoder decodeObjectForKey:KEY_IS_PURCHASED];

        self.Titel = [aDecoder decodeObjectForKey:KEY_TITEL];
    }
    return self;
}

The leak appears in instruments on the device in that line:

self.Titel = [aDecoder decodeObjectForKey:KEY_TITEL];

KEY_TITEL is:

#define KEY_TITEL @"Titel"

and self.Titel is:

@property (nonatomic, retain) NSString *Titel;

it is synthesize and it is released in dealloc.

I don't have any idea where the leak is come from. Can you help me out please...

thank you xnz

Dave DeLong · Accepted Answer · 2011-04-03 06:55:51Z

3

You're mis-interpreting what Instruments is telling you.

It is not telling you where you leaked an object.

It is telling you where you created an object that was eventually leaked.

Reanalyze the data from Instruments accordingly. (You're likely missing a [Titel release] call in your -dealloc method)

answered Apr 3, 2011 at 6:55

Dave DeLong

243k58 gold badges452 silver badges498 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Laurent Etiemble · Accepted Answer · 2010-11-23 14:06:21Z

0

Do have you assign a value to Titel before initWithCoder execution ? Maybe in super class ? The leak does not seem to be linked to the initWithCoder execution, but to a previous assignment.

answered Nov 23, 2010 at 14:06

Laurent Etiemble

28.1k5 gold badges59 silver badges81 bronze badges

1 Comment

xnz Over a year ago

If I don't find the archived object, I assign it from a Dictionary. But if I do so then initWithCoder is not called. Superclass is NSObject, so I don't assign it there.

Collectives™ on Stack Overflow

NSCoding leak problem with initWithCoder

2 Answers 2

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related