CFNetwork sendDidReceiveDataCallback leaking?

[bonehead]

In beta8 I'm seeing CFNetwork sendDidReceiveDataCallback leaving a whole bunch of objects sitting around in the my app's main autorelease pool. I'm creating some NSURLConnection objects and releasing them when finished...however, it looks like they're leaving junk in my autorelease pool that eventually causes the app to run out of memory.

(I've even tried creating a new autorelease pool before creating the NSURLConnection objects, and then draining the pool when finished with those objects: no luck.)

Anyone else seeing this?

[jonc]

I have also been noticing this.

Is it usually some sort of connection object that wasn't allocated by any of your code? That is what I am seeing.

It doesn't seem to be happening often enough to cause me memory headaches, but my program only uses the network connection intermittently. I am pretty sure I am doing everything properly too.

I am about to walk out the door at work, but I will private message you an instruments save showing the leak later because I am curious if we are leaking the same object with a similar trace.

[jonc]

Sorry I haven't forgotten about this, I have just been insanely busy trying to get my apps done and getting ready to move 12 hours away the day after the app store launches (crazy I know).

Anyway, so I was trying to reproduce this leak at home on my laptop and I couldn't get it to show up using the simulator. I know I was running on the device the other day at work when it was happening though. I don't have certificates on my laptop and don't want to go to the trouble, but I will check it again at work. Are you only seeing this problem on the device?

[bonehead]

I'm seeing very significant leaks on the device, less significant (but similar) leaks on the simulator.

On the simulator I see "GeneralBlock-32768" hanging around in ObjectAlloc

On the device I see both those and other "GeneralBlock-Foo" of various sizes.

[jonc]

Originally Posted by bonehead

I'm seeing very significant leaks on the device, less significant (but similar) leaks on the simulator.

On the simulator I see "GeneralBlock-32768" hanging around in ObjectAlloc

On the device I see both those and other "GeneralBlock-Foo" of various sizes.

I am seeing the same thing. Sometimes the GeneralBlocks vary in size, but it sounds like the same thing.

[Zunnun]

Same for me - leaks!

[imho]

This problem had been reported in the Apple Mailing before. Seems like the only way is to use the synchronous methods.

A similar problem exists if you open CFWriteStream or CFReadSteam asynchronously. It will sometimes leak 3.5KB. The funny thing is, it doesn't leak all the time. I suspect it has nothing to do with the networking part of the SDK. Something in the SDK's asynchronous handling messed up...