Anyone else find that NSURLConnection seems to be a huge memory hog?
As soon as I use it my RPRVT goes from ~3M to ~13M which seems a bit
more then excessive to me. Not to mention that it seems to leave 2
threads hanging around, even after everything has been released.
I probably wouldn't care if it used up a bunch of RAM/threads and then
released when it was done, but it seems pretty crazy that a class that
is probably used by most to do tiny requests uses and keeps such a
huge chunk of resources.
Anyone else notice this? Or better yet found a nice solution?
--
Paul Haddad (email@hidden email@hidden)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
