From bug 1067437: (In reply to Jay from comment #21) > I see that DrainOutput() just returns without doing anything once it sees > error condition so it should not impact the functionality. However, ideally, > the DrainOutput() thread should be stopped while codec re-configuring is > taking place. Can this be done easily? Not too hard though one must be careful with multithreaded/locked code; likely just wait on a monitor if a new state variable (mPaused) is true. Gotta be careful we don't miss transitions from Paused to Ending, etc. A new bug; since there's no negative impact other than some CPU and logs in a rare-ish case this can get done later. +++ This bug was initially created as a clone of Bug #1067437 +++
You need to log in before you can comment on or make changes to this bug.