0
0

It appears that this routine will wait until any outstanding stream callback completes. This appears to be the case regardless of whether or not the stream was originally opened with the FSOUND_NONBLOCKING flag.

Now this may not sound like a big deal, but my callback routine was coded to wait on a system lock.

Under certain application conditions, a different part of the application would stop the stream and then a close attempted. That code also would take out the same lock. Hence they (very very hard to find) deadlock situation occurred in rare circumstances, when the application will try and stop and close the stream just as the stream completed playing.

Beware!

Cheers
Ronny

  • You must to post comments
0
0

yes it has to wait because it cant free memory while the stream thread is still using it.

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.