Process requests to bind TtsStreamFactory in order
Scenario: - two (or more) component extensions request binding of TtsStreamFactory - requests are received in TtsService - there is only one concrete Receiver instance - each request closes the connection to any previously bound TtsStreamFactory connections As a result, any previous connections will be closed prematurely e.g. before the extension can call createGoogleTtsStream. Fix this by keeping around all PendingReceiver instances and process them whenever we can. Specifically, once the extension creates a specific tts stream, process the next pending request for a factory. Test: manual. Observe errors without this change in some rare timing instances where an extension gets a tts stream factory but is disconnected before creating a stream. Observe no such error with this change. R=dmazzoni@chromium.org Fixed: 1131321 Change-Id: Ie0a2803fff809ada42038001fa015e1a6fb63e0e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2561540 Commit-Queue: David Tseng <dtseng@chromium.org> Reviewed-by:Alexander Alekseev <alemate@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#832545}
Showing
Please register or sign in to comment