Re: static analyzers says I'm leaking, I _think_ I'm not
Re: static analyzers says I'm leaking, I _think_ I'm not
- Subject: Re: static analyzers says I'm leaking, I _think_ I'm not
- From: Greg Parker <email@hidden>
- Date: Wed, 06 May 2015 14:12:47 -0700
> On May 6, 2015, at 1:57 PM, Michael David Crawford <email@hidden> wrote:
>
> // LifeGrid.h
> @property (assign, nonatomic) GridCycler *cycler;
>
> // Lifegrid.m - init
> self.cycler = [[GridCycler alloc] initWithGrid: self]; // Potential
> leak of an object
> if ( nil == self.cycler ) goto cycler_failed;
>
> // dealloc
> [self.cycler release];
>
> Expanding the "potential leak" message yields:
>
> 1. assuming 'self' is not nil
>
> 2. method returns Objective-C object with +1 retain count
>
> 3. Object leaked: allocated object is not references later in this
> execution path and has a retain count of +1.
>
> Isn't that what I want? I should be taking ownership of it with
> "alloc/initWithGrid".
>
> (initWithGrid doesn't do a cyclic retain.)
Which version of Xcode are you using? The static analyzer in Xcode 6.3 has several bugs in retain count analysis and not all of them are fixed in Xcode 6.3.1.
--
Greg Parker email@hidden Runtime Wrangler
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden