Re: Odd EXEC_BAD_ACCESS after executing URLRequest
Re: Odd EXEC_BAD_ACCESS after executing URLRequest
- Subject: Re: Odd EXEC_BAD_ACCESS after executing URLRequest
- From: marc hoffman <email@hidden>
- Date: Tue, 30 Dec 2008 19:10:34 +0100
Jason,
On Tue, Dec 30, 2008 at 10:10 AM, marc hoffman <email@hidden>
wrote:
while (!done)
{
[[NSRunLoop currentRunLoop]
runMode:NSDefaultRunLoopMode
beforeDate:[NSDate dateWithTimeIntervalSinceNow:timeout]];
}
Since you want the request to happen synchronously, why not just use
+[NSURLConnection sendSynchronousRequest:returningResponse:error:] ?
mainly because i want (need) the feedback callbacks, so i can get the
anticipated size and progress of longer downloads.
Recursively pumping the run loop like that in the default mode is
discouraged. I don't know the specifics of why, but crashes such as
you're seeing could be part of it.
do you have any references on this and what could/should be done
internally? i saw that there are some runloop options (ie a mode)
specifically for NS(URL)Connections as well, but it seems that one
doesn't exist on the iPhone (contrary to docs), nor could i find any
info on what this would do differenly...
thanx,
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