Thanks, Jeff, others are also saying that implementing this method
doesn't always fix the problem. Which makes sense: presumably Apple's
implementation amounts to "return request;", so it is hard to see how
that method could be at the root of the problem.
I hope everybody is filing bug reports with Apple. I just can't believe
that Apple could have introduced a flaw in something so basic.
Jeff Johnson wrote:
I'm not sure that this is the full story. My app Vienna implements
connection:willSendRequest: redirectResponse: at AsyncConnection.m: 396
http://vienna-rss.svn.sourceforge.net/viewvc/vienna-rss/trunk/2.3.0/AsyncConnection.m?view=markup
However, I'm seeing crash reports from users on 10.5.7, for example:
http://dl.getdropbox.com/u/32952/ViennaCrash.txt
-Jeff
On Jun 1, 2009, at 11:23 AM, Dennis Hartigan-O'Connor wrote:
Thanks, Andrew,
I believe that Colin Gray got to the bottom of this at Stack Overflow:
http://stackoverflow.com/questions/916718/nsurlconnection-crashing-under-10-5-7
Dennis
Andrew Farmer wrote:
On 27 May 2009, at 18:20, Dennis Hartigan-O'Connor wrote:
I have a very similar problem: my simple program that downloads
stock prices has been working fine but intermittently crashes on
10.5.7, whether I use sendSynchronousRequest or
stringWithContentsOfURL. For me, too, everything is fine for 10-15
minutes and then the program crashes.
Here is the crash log from the crashed thread:
Thread 1 Crashed:
0 libobjc.A.dylib 0x965c3688 objc_msgSend + 24
1 com.apple.CoreFoundation 0x946cc581
_CFStreamSignalEventSynch + 193
2 com.apple.CoreFoundation 0x946ba595
CFRunLoopRunSpecific + 3141
3 com.apple.CoreFoundation 0x946bac78
CFRunLoopRunInMode + 88
4 com.apple.Foundation 0x9058c530
+[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:]
+ 320
5 com.apple.Foundation 0x90528e0d -[NSThread main]
+ 45
6 com.apple.Foundation 0x905289b4
__NSThread__main__ + 308
Any ideas out there? I can't believe this isn't happening to lots
of people.
The symptoms described in the original thread all pointed strongly to
a latent memory management issue that's being triggered by changes in
the URL loading code. Does your application print any console output
before (or as) it's crashing? If this doesn't point straight at
anything, try running your application under MallocDebug.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
