Re: CFNetwork crash!
Re: CFNetwork crash!
- Subject: Re: CFNetwork crash!
- From: Becky Willrich <email@hidden>
- Date: Tue, 16 Jul 2002 09:54:33 -0700
It seems to be dying because socketCallBack is trying to retain a
disposed object. Am I not allowed to dispose the CFStreams in the
callback? If not, when am I supposed to?
It should be legal to dispose of the CFStreams in the callback, and I
don't recall any bugs along this line in Puma, but that doesn't mean
there aren't any. However, your backtrace looks very much like an
over-release of one of the socket streams; any chance from your end
that's the case?
BTW, if you're working in obj-c, one way to quickly check your theory
that the problem is disposing of the CFStream inits own callback is to
call [(id)otEndpointPtr->writeStream autorelease]; that will
effectively delay the release of the object until processing has
returned to the run loop. Failing that, you'd have to somehow mark the
stream for later disposal or signal yourself via the run loop to
destroy it.
Hope that helps,
REW
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.