Safely removing an I/O proc
Safely removing an I/O proc
- Subject: Safely removing an I/O proc
- From: "Timothy J. Wood" <email@hidden>
- Date: Fri, 6 Jun 2003 00:24:43 -0700
I'm running into rare crashes where an I/O proc seems to be accessing
data in my I/O proc connection refcon (which is some random pointer of
interesting data).
I was hoping that setting the input callback/refcon would not return
until any pending I/O proc invocation on that input was finished. Is
this not true?
If the removal really isn't thread-safe, what is the recommended way
of determining when you can deallocate data in your refcon? I could
just wait for 'a while' before destroying it, but there has to be a
cleaner way -- does signing up for property change notifications seem
like a better way?
Pointers to documentation would be just dandy -- I've been looking,
but I haven't had any luck finding info on this topic.
-tim
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.