Re: crashing in calls to AudioConverter on 10.3.9
Re: crashing in calls to AudioConverter on 10.3.9
- Subject: Re: crashing in calls to AudioConverter on 10.3.9
- From: William Stewart <email@hidden>
- Date: Wed, 22 Mar 2006 16:39:30 -0800
The AudioConverter is intentionally not thread safe - that is, you
can't be in one thread, calling the Reset call, while in another
thread calling the convert call. If you are sharing an instance of
the converter in multiple threads, you'll have to ensure single
access through a mutex or some similar technique.
Bill
On 22/03/2006, at 9:27 AM, Christopher Ashworth wrote:
Hello,
I have an app that runs on 10.3.9 and above. I am encountering
(and am receiving crash reports) concerning an intermittent crash
that so far only appears to occur on 10.3.9, and not on 10.4+.
The basic context is this: One or more sound files are being
loaded into a buffer and played back. The user is able to "seek"
to various positions in a sound file. (The app may be found at
http://figure53.com if you would like to see the full context.)
I have not yet been able to produce sample code that induces the
crash definitively, but I am able to produce it regularly if I
exercise the code that performs this seeking function.
I included crash log output when I tried to post this to the list
before, but that email was rejected by the list admin, so I am
resending without log output. The basic gist of the logs was that
each crash is occurring somewhere within the AudioConverter*
functions, either in AudioConverterFillComplexBuffer or
AudioConverterReset. The traceback is slightly different on each
crash I've looked at.
I realize this may not be enough information to diagnose the
problem, but my questions are:
1) Is there a reason that anyone would know offhand that would
explain why I'm seeing this only on 10.3.9 so far? (e.g. was there
a bug fix in 10.4+ that may be relevant?) I am particularly
curious about this, because it does seem very suspicious that I am
only seeing the problem on 10.3.9.
2) Does the pattern of these crashes indicate some poor practice I
may be following? For example, I have been careful to place locks
around anything that messes with the relevant buffers, but it is
possible something has slipped my notice.
3) Is there a good way I can produce more helpful debugging
information?
Thanks much,
Chris
_______________________________________________
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
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
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