Hi Rob, we talked about this issue where onComplete within audio statements engages even when the audio that is set to play has been disposed. Your suggestion (which works) is to create a flag variable to check whether the audio had already been disposed. Obviously doing this flag check is more of a work around but this morning I read this in the 2013.1146 release notes of the Daily Build:
Core - fix various crashes associated with
disposing of audio streams; issue error messages when invalid (usually
previously disposed) streams are passed to various audio. APIs - fixes
casenum 24229 et al
Does this fix our wild onComplete issue?