Does anyone else experience leaks of doom with the NSURLConnection class? I have read a lot about this over the net, but the articles I see are over 2 years old. Has this been rectified and it is just bad coding on my part?!!
I have read that changing from Sync to Async is better - but still getting issues, I have read to include:
I found in my app that the leak was more of a one-time thing than a leak of doom. My app submits files of data to the Google docs API, and I found that no matter how many files I submit, each with a new NSURLConnection created, I only saw memory leaked once. Since it did not build up, I figured it would never be an issue that would crash my app.
I found in my app that the leak was more of a one-time thing than a leak of doom. My app submits files of data to the Google docs API, and I found that no matter how many files I submit, each with a new NSURLConnection created, I only saw memory leaked once. Since it did not build up, I figured it would never be an issue that would crash my app.
What is happening in your app?
Hi
Mine is more of a download app rather than upload. I have a loop that runs an async request, after each request I release and create a new object to get the next packet. After a couple of requests I see a huge spike on the leaks and looking I see its the CFNetwork class. It only appears to be on the device. The simulator doesnt appear to leak.
NSURLConnection Leak Central
Linear Mode
