I thought it was [[[id alloc] init] autorelease]; and I thought of another idea that it could of been, I clicked the button twice and because NSURLConnection is a thread based connection system, it could of been releasing at the same time as it was checking, so I added locks.
On Jan 9, 2010, at 7:23 PM, Paul Bruneau wrote:
> -new is the equivalent of an -alloc and -init, so you already own the object
> at that point. Then you retain it, so I think that's more retaining than you
> want to do.
>
> That's my guess
>
> Sent from my iPhone--typos caused by auto-correct
>
> On Jan 9, 2010, at 8:15 PM, "Mr. Gecko" <grmrge...@gmail.com> wrote:
>
>> Hello, I'm going through leak checking and it seems that a if statement is
>> causing a leak that's 32 Bytes big. My if statement is
>>
>> if (connections==nil) {
>> connections = [[NSMutableArray new] retain];
>> }
>>
>> It says that if (connections==nil) is leaking 32 bytes which I have no idea
>> how that could be possible. Yes I'm releasing connections after I'm done
>> using it.
>> Should I just ignore this? Thanks,
>> Mr. Gecko
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
