Re: Any official workaround for NSURLConnection leaks on Tiger
Re: Any official workaround for NSURLConnection leaks on Tiger
- Subject: Re: Any official workaround for NSURLConnection leaks on Tiger
- From: Stéphane Sudre <email@hidden>
- Date: Thu, 21 Aug 2008 14:30:19 +0200
On Aug 19, 2008, at 8:37 PM, Ladd Van Tol wrote:
On Aug 18, 2008, at 7:12 AM, Stéphane Sudre wrote:
Hi,
NSURLConnection code is leaking instances of NSDictionary, NSString
and other things on Tiger (10.4.11) when you run a GET request. No
leak on Leopard.
It seems odd that this would be happening, as so many other apps use
NSURLConnection successfully.
Unfortunately, it's not that odd if you consider there are other known
issues (memory or not) with NSURLConnection in Tiger:
http://www.red-sweater.com/blog/452/nsurlconnection-crashing-epidemic
https://bugs.launchpad.net/sparkle/+bug/228449
I have already used some tips related to these reports (caching policy
for instance) but it's apparently not enough.
Still, you might consider using libcurl -- I've often had to do this
when the NSURL* classes proved inadequate.
Thanks for the suggestion.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden