Re: Crash in ExtAudioFile API
Re: Crash in ExtAudioFile API
- Subject: Re: Crash in ExtAudioFile API
- From: Shalab Goel <email@hidden>
- Date: Fri, 17 Aug 2012 10:51:59 -0700
It sounds like there is a possibility of some singleton object (or state object of sorts) being utilized under the covers in EAF implementation that is not thread safe. If such is the case, it is indeed a nasty issue to find out about..
Will be good to hear what comes out of this, as this issue is dug deeper.
Thanks
Shalab
On Fri, Aug 17, 2012 at 5:17 AM, patrick machielse
<email@hidden> wrote:
Op 17 aug. 2012, om 08:32 heeft tahome izwah <email@hidden> het volgende geschreven:
> From what I have learned EAF isn't thread safe (never was). You
> shouldn't be accessing the same EAF object from different threads
> unless you can be absolutely certain that the access is sequential
> (you could use @synchronized for this if you're using ObjC).
That isn't the problem here. Each ExtAudioFile object is used from one thread only. In the crash log we're creating a fresh EAF in ExtAudioFileOpenURL() on thread 13 while on thread 1 ExtAudioFileSetProperty() is called -- necessarily with a different EAF object.
p.
--
Patrick Machielse
Hieper Software
http://www.hieper.nl
email@hidden
_______________________________________________
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