• 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
Re: Any official workaround for NSURLConnection leaks on Tiger
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Any official workaround for NSURLConnection leaks on Tiger


  • Subject: Re: Any official workaround for NSURLConnection leaks on Tiger
  • From: Mark Pauley <email@hidden>
  • Date: Tue, 19 Aug 2008 11:28:22 -0700

This is pretty harrowing news Stéphane... I'm not so sure that there is a good workaround for you with NSURLConnection.

If you can find me the allocation stack traces, I might be able to pinpoint the source of these leaks, that's about all I can do.


On Aug 19, 2008, at 3:17 AM, Stéphane Sudre wrote:

Le Aug 18, 2008 à 8:23 PM, Mark Pauley a écrit :

How are you seeing these leaks?

With Activity Monitor, RSIZE keeps on increasing every time a connection is made.


With leaks, I can see that dozens (actually hundreds because I'm using multiple NSURLConnections) of NSDictionarys, NSStrings are leaking. Typically, I'm doing 5-10 connections per minute to download very small file (100 Bytes max) and I'm probably leaking up to 1 MB per minute. The leak happens when the connection is run.

Are you using object alloc?

Nope, leaks. It's easier for me to find problems this way but if you have tips to do that with object alloc, they are welcome.


What happens if you wrap your NSURLConnection calls with an NSAutoreleasePool instantiation?

I have already wrapped the callbacks and the requestWithURL: code around NSAutoreleasePools.


As I said, no leaks on Leopard. And I don't have specific paths for Tiger in my code.

I might add that I have 2 implementations of my networking code:

- NSURL with loadResourceDataNotifyingClient: (which is said to be deprecated and which is why I moved to NSURLConnection)

- NSURLConnection with requestWithURL:

Both cases leak on Tiger.

My issue being that since my process can be running 24/7, I can't allow any leaks.

--
Stephane _______________________________________________
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

_Mark email@hidden




_______________________________________________ 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
References: 
 >Any official workaround for NSURLConnection leaks on Tiger (From: Stéphane Sudre <email@hidden>)
 >Re: Any official workaround for NSURLConnection leaks on Tiger (From: Mark Pauley <email@hidden>)
 >Re: Any official workaround for NSURLConnection leaks on Tiger (From: Stéphane Sudre <email@hidden>)

  • Prev by Date: Re: Any official workaround for NSURLConnection leaks on Tiger
  • Next by Date: Re: Any official workaround for NSURLConnection leaks on Tiger
  • Previous by thread: Re: Any official workaround for NSURLConnection leaks on Tiger
  • Next by thread: Re: Any official workaround for NSURLConnection leaks on Tiger
  • Index(es):
    • Date
    • Thread