Fwd: ExtAudioFileDispose blocking
Fwd: ExtAudioFileDispose blocking
- Subject: Fwd: ExtAudioFileDispose blocking
- From: Ethan Funk <email@hidden>
- Date: Tue, 6 Apr 2010 11:33:54 -0700
No bug report as I want to rule out a problem with my code first. This is on OS X 10.6.2. If you go back through the mail list archive there is a more extensive explanation as to what I am doing... I did not include that in the recent post because the backtrace AND the explanation would have exceeded the e-mail size limit for this list.
In brief, I open with ExtAudioFile, then hand off to a thread which reads using ExtAudioFile to keep an audio ring buffer full, then, when finished, I stop/join the reading thread through a flag and pthread_join, then Dispose of the ExtAudioFile object. I don't think there are any threading problems with this approach... no concurrent access to the ExtAudioFile object.
Ethan...
On Apr 6, 2010, at 10:51 AM, William Stewart wrote:
> Ethan
>
> Do you have a bug report for this? Could you give us a description of exactly what is going on. For instance, are you just using ExtAudioFile to open the file then we read from the disk directly and know where to look further for the problem. If you are using ExtAudioFile to wrap a file opened Audio File and callbacks, then that is a different debugging path
>
> Presuming you are using ExtAudioFile to open the object, so you go through our read calls... James' initial thought is that you have disposed the ExtAudioFile object, but then go to make a read using it - and thus the problem you are encountering. We're not sure that we could protect against this, because the file object could be getting disposed while you are even within the process of doing a read. It is an important consideration that the ExtAudioFile is not thread safe (which I believe you understand, just to repeat it though).
>
>
> Bill
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden