• 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: Odd EXEC_BAD_ACCESS after executing URLRequest [SOLVED]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Odd EXEC_BAD_ACCESS after executing URLRequest [SOLVED]


  • Subject: Re: Odd EXEC_BAD_ACCESS after executing URLRequest [SOLVED]
  • From: marc hoffman <email@hidden>
  • Date: Wed, 7 Jan 2009 16:43:45 +0100

Jason,

The way you've allocated the connection, it should start
automatically.  You shouldn't need to call -start manually.  This
*might* be causing some issues.  The documentation doesn't say not to
call it on a connection that is already started, but there might be a
bug.  Try removing this call to see if it helps at all.

wow, that was indeed it. odd, i could have /sworn/ i had seen a separate class method in the docs with a "shouldStart" parameter, and that this one was supposed to not start it. teaches me to trust my memory ;P


anyways, all working now, thanks a lot!

marc
_______________________________________________

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: Odd EXEC_BAD_ACCESS after executing URLRequest [SOLVED]
      • From: "Jason Foreman" <email@hidden>
References: 
 >Re: Odd EXEC_BAD_ACCESS after executing URLRequest (From: marc hoffman <email@hidden>)
 >Re: Odd EXEC_BAD_ACCESS after executing URLRequest (From: "Jason Foreman" <email@hidden>)

  • Prev by Date: Re: Convert GWorldPtr into a NSImage
  • Next by Date: Re: Odd EXEC_BAD_ACCESS after executing URLRequest [SOLVED]
  • Previous by thread: Re: Odd EXEC_BAD_ACCESS after executing URLRequest
  • Next by thread: Re: Odd EXEC_BAD_ACCESS after executing URLRequest [SOLVED]
  • Index(es):
    • Date
    • Thread