ansaurus

Question

Releasing connection in connectionDidFinishLoading cause bad instruction

Answer 1

A:

This is a double release error. It means either you didn't retain an object enough times, or you sent it too many release messages.

Mike Weller 2010-07-15 14:28:24

I understand the nature of error, but all I do is just create `NSConnection` with `connectionWithRequest` and then release in those 2 delegates. The rest of the bodies of delegate methods are empty.

Michael 2010-07-15 14:31:53

The general rule is: If you don't create objects using alloc, and don't retain objects, you don't have to release them. They will magically disappear when no-one needs them anymore (with NSAutoReleasePool being the magician and autorelease being the magic spell)

mvds 2010-07-15 14:49:36

Answer 2

+1 A:

If you doesn't retain the object you receive from [NSConnection connectionWithRequest:] then you must not call release on it.

Claus Broch 2010-07-15 14:44:57

ansaurus

tags:

views:

answers:

Releasing connection in connectionDidFinishLoading cause bad instruction

related questions