Re: Odd EXEC_BAD_ACCESS after executing URLRequest [SOLVED]

2009-01-07 Thread Jason Foreman
On Wed, Jan 7, 2009 at 9:43 AM, marc hoffman wrote: > > 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 Well, your memory isn't *t

Re: Odd EXEC_BAD_ACCESS after executing URLRequest [SOLVED]

2009-01-07 Thread marc hoffman
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 ca

Re: Odd EXEC_BAD_ACCESS after executing URLRequest

2009-01-06 Thread Jason Foreman
Hi Marc, On Tue, Jan 6, 2009 at 2:42 AM, marc hoffman wrote: > > any other ideas? > I did notice one thing from your original code: > NSURLConnection *conn = [[NSURLConnection connectionWithRequest:request > delegate:self] retain]; > @try > { > [conn start]; The way you

Re: Odd EXEC_BAD_ACCESS after executing URLRequest

2009-01-06 Thread marc hoffman
Jason, +[NSURLConnection sendSynchronousRequest:returningResponse:error:] ? 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. same happens when i frun the code "proper" as

Re: Odd EXEC_BAD_ACCESS after executing URLRequest

2008-12-31 Thread marc hoffman
Jacob, Are you sure you are not accidentally triggering two 'send message' calls concurrently. One of the most common causes of this problem is that your second request is over-writing the variables of an already in progress request. Check that done is not set to yes when you call your '

Re: Odd EXEC_BAD_ACCESS after executing URLRequest

2008-12-30 Thread Jacob Rhoden
On 31/12/08 3:10 AM, marc hoffman wrote: i'm hoping someone has an idea here - i'm seeing odd crashes after doing URL requests. the first request completes fine (up to it triggering connectionDidFinishLoading:), but shortly after or while doing a subsequent request... Are you sure you are no

Re: Odd EXEC_BAD_ACCESS after executing URLRequest

2008-12-30 Thread marc hoffman
Jason, On Tue, Dec 30, 2008 at 10:10 AM, marc hoffman wrote: while (!done) { [[NSRunLoop currentRunLoop] runMode:NSDefaultRunLoopMode beforeDate:[NSDate dateWithTimeIntervalSinceNow:timeout]]; } Since you want the request to happen synchronous

Re: Odd EXEC_BAD_ACCESS after executing URLRequest

2008-12-30 Thread Jason Foreman
On Tue, Dec 30, 2008 at 10:10 AM, marc hoffman wrote: >while (!done) >{ >[[NSRunLoop currentRunLoop] runMode:NSDefaultRunLoopMode > beforeDate:[NSDate dateWithTimeIntervalSinceNow:timeout]]; >} > Since you want the request to happen synchronousl

Odd EXEC_BAD_ACCESS after executing URLRequest

2008-12-30 Thread marc hoffman
Hi, i'm hoping someone has an idea here - i'm seeing odd crashes after doing URL requests. the first request completes fine (up to it triggering connectionDidFinishLoading:), but shortly after or while doing a subsequent request, i get a EXC_BAD_ACCESS in what seems to be a secondary work