• 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: [SOLVED] Re: Help with NSURLConnection memory fault
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [SOLVED] Re: Help with NSURLConnection memory fault


  • Subject: Re: [SOLVED] Re: Help with NSURLConnection memory fault
  • From: Jens Alfke <email@hidden>
  • Date: Wed, 14 Oct 2009 19:51:37 -0700


On Oct 14, 2009, at 7:43 PM, Stuart Malin wrote:

Just a "lucky" coincidence that the memory where the dealloc'd NSURLConnection had lived was still the (now defunct) object, so it went through its motions again, and tried to release the delegate a second time.

The MallocScribble environment variable will help avoid that sort of "luck", by filling all deleted blocks with 0x55. I always set it in the executable inspector in any project I'm working on.


—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


References: 
 >Help with NSURLConnection memory fault (From: Stuart Malin <email@hidden>)
 >Re: Help with NSURLConnection memory fault (From: Jens Alfke <email@hidden>)
 >[SOLVED] Re: Help with NSURLConnection memory fault (From: Stuart Malin <email@hidden>)

  • Prev by Date: Re: iPhone/iPod Device Detection Necessary for App Approval?
  • Next by Date: shared preferences.
  • Previous by thread: [SOLVED] Re: Help with NSURLConnection memory fault
  • Next by thread: Can I make custom pasteboard type for an object reference?
  • Index(es):
    • Date
    • Thread