Releasing objects causes BAD_ACCESS

• Meik Schuetz Releasing objects causes BAD_ACCESS Jul 07 2008, 23:38
  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
• Jonathan del Strother Re: Releasing objects causes BAD_ACCESS Jul 07 2008, 23:44
  On Mon, Jul 7, 2008 at 10:38 PM, Meik Schuetz <cocoa...> wrote:
  

  > 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?
  >
  

  
  NSZombieEnabled is a good start -
  http://developer.apple.com/technotes/tn2004/tn2124.html#SECFOUNDATION
• Randall Meadows Re: Releasing objects causes BAD_ACCESS Jul 07 2008, 23:49
  On Jul 7, 2008, at 3:44 PM, Jonathan del Strother wrote:
  

  > On Mon, Jul 7, 2008 at 10:38 PM, Meik Schuetz <cocoa...>
  > wrote:
  >> 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?
  >
  > NSZombieEnabled is a good start -
  > http://developer.apple.com/technotes/tn2004/tn2124.html#SECFOUNDATION
  

  
  See also "Technical Note TN2124 - Mac OS X Debugging Magic":
  <http://developer.apple.com/technotes/tn2004/tn2124.html>
• Randall Meadows Re: Releasing objects causes BAD_ACCESS Jul 07 2008, 23:54
  On Jul 7, 2008, at 3:49 PM, Randall Meadows wrote:
  
  

  >> NSZombieEnabled is a good start -
  >> http://developer.apple.com/technotes/tn2004/tn2124.html#SECFOUNDATION
  >
  > See also "Technical Note TN2124 - Mac OS X Debugging Magic":
  > <http://developer.apple.com/technotes/tn2004/tn2124.html>
  

  
  Heh, which now I see was the aforementioned link...I just saw the
  tn2004 and didn't read the URL further.
• Scott Ribe Re: Releasing objects causes BAD_ACCESS Jul 08 2008, 04:09
  > the connection object as well as the receivedData object are released
  > in the connectionDidFinishLoading delegate
  

  
  The sample also retains receivedData after creating the connection. Did you
  do that? And did you create the connection using alloc initxxx?
  
  --
  Scott Ribe
  <scott_ribe...>
  http://www.killerbytes.com/
  (303) 722-0567 voice