Re: ExtAudioFileRead Crash
Re: ExtAudioFileRead Crash
- Subject: Re: ExtAudioFileRead Crash
- From: Peter Castine <email@hidden>
- Date: Tue, 13 Oct 2009 18:18:55 +0200
What is the call stack that ends in the "CrashIfClient..." - we have
that in a number of places, and knowing which one you are hitting
can tell us where you are crashing at least (potentially which
buffer is bad)
Here's one:
----
Thread 45 Crashed:
0 ....audio.toolbox.AudioToolbox 0x9918e651
CrashIfClientProvidedBogusAudioBufferList + 73
1 ....audio.toolbox.AudioToolbox 0x991e19fa ExtAudioFileRead + 66
2 ...coustic.myApp 0x0000c0e0 ChunkReadCallback + 260
3 ...coustic.myApp 0x00017b0f WorkerThreadStartFunc + 63
4 libSystem.B.dylib 0x9838cf39 _pthread_start + 345
5 libSystem.B.dylib 0x9838cdbe thread_start + 34
----
ExtAudioFileRead+66 and CrashIfClient…+73 are also listed in my other
logs.
As we previously noted, you can't be accessing the same ext audio
file object from different threads at the same time - between your
buffer and the file is an audio converter, and it has potentially
alot of state that is NOT protected from simultaneous access. If
this is being accessed from more than one thread, it is quite likely
that a buffer is being overidden.
This is what's worrying me. Jean-Daniel pointed out earlier that some
of the stacks were pointing a finger at my code doing something wrong.
To my horror I've just found something where he might well be right.
I'm going to try to address that potential problem now. If the call
stack above provides additional insight, so much the better.
Thanks -- P.
_______________________________________________
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