• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
NSURLConnection memory hog?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NSURLConnection memory hog?


  • Subject: NSURLConnection memory hog?
  • From: "Paul Haddad" <email@hidden>
  • Date: Fri, 10 Nov 2006 22:15:37 -0600

Hi All,

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:
This email sent to email@hidden


  • Follow-Ups:
    • Re: NSURLConnection memory hog?
      • From: Jerry Krinock <email@hidden>
  • Prev by Date: [Moderator] EOT: Re: Authorization code fails in Leopard
  • Next by Date: Re: NSURLConnection memory hog?
  • Previous by thread: Re: How to get user ID (501, 502, etc.)
  • Next by thread: Re: NSURLConnection memory hog?
  • Index(es):
    • Date
    • Thread