Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Releasing objects causes BAD_ACCESS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Releasing objects causes BAD_ACCESS

Subject: Releasing objects causes BAD_ACCESS
From: Meik Schuetz <email@hidden>
Date: Mon, 7 Jul 2008 22:38:38 +0100

Dear all,

according to the document

http://developer.apple.com/documentation/Cocoa/Conceptual/URLLoadingSystem/Tasks/UsingNSURLConnection.html

the connection object as well as the receivedData object are released in the connectionDidFinishLoading delegate. However, while debugging, I receive an BAD_ACCESS violation doing the release. Can anyone please give me some insight on why this is happening? Is there any strategy/ debugging tool that helps me to find objects that should have been released or should I just rely on GC?

Thanks so much
Best regards
Meik

_______________________________________________

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


Follow-Ups:

Re: Releasing objects causes BAD_ACCESS
From: Scott Ribe <email@hidden>
Re: Releasing objects causes BAD_ACCESS
From: "Jonathan del Strother" <email@hidden>


Prev by Date:
Re: More CALayer Questions

Next by Date:
Re: Releasing objects causes BAD_ACCESS

Previous by thread:
Re: Sub-classing NSAtomicStore

Next by thread:
Re: Releasing objects causes BAD_ACCESS

Index(es):

Date
Thread