• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Help with NSURLConnection memory fault
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Help with NSURLConnection memory fault


  • Subject: Re: Help with NSURLConnection memory fault
  • From: Jens Alfke <email@hidden>
  • Date: Wed, 14 Oct 2009 16:24:05 -0700

It looks as though your object (the delegate) got dealloced too early, before the NSURLConnection finished loading. This shouldn't be possible, since the connection object retains the delegate, but you may have too many release calls to it someplace.

What I would do next is set a breakpoint in your class's dealloc method, and also in its -connectionDidFinishLoading: and - connection:didFailWithError:, and see which gets called first.

—Jens_______________________________________________

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:
    • [SOLVED] Re: Help with NSURLConnection memory fault
      • From: Stuart Malin <email@hidden>
References: 
 >Help with NSURLConnection memory fault (From: Stuart Malin <email@hidden>)

  • Prev by Date: Re: SelectedRowIndexes
  • Next by Date: Re: SelectedRowIndexes
  • Previous by thread: Help with NSURLConnection memory fault
  • Next by thread: [SOLVED] Re: Help with NSURLConnection memory fault
  • Index(es):
    • Date
    • Thread