gecko-dev/media/webrtc
Jean-Yves Avenard 5be22726b0 Bug 1650696 - P4. Remove the expectation for a MediaDataDecoder to work on a specified TaskQueue. r=jolin
It will now be up to the caller to determine where the decoder is going to run. This allows to simplify the audio decoders so that they can run synchronously and be wrapped in a Wasm sandbox (which doesn't support multi-threading)

The structure guarantees that all MediaDataDecoder methods are called on the same thread it's been initialised.

To achieve this, wherever a MediaDataDecoder was created, we wrap it in a MediaDataDecoderProxy that ensures that all methods are running on the given thread.

We keep the behaviour of all methods in all MediaDataDecoder to assert that they are running on the expected thread for diagnostic purposes. It could go in the future.

Video decoders that could block excessingly the thread on which they are called are made to run on their own task queue.
The Apple decoder is mostly entirely asynchronous, with the exception of the drain method which could block.
We exclude the android and omx decoders are the framework they use is 100% asynchronous and already operate on another thread.

Differential Revision: https://phabricator.services.mozilla.com/D86929
2020-08-17 23:52:21 +00:00
..
gn-configs Bug 1658397 - Add gn configs for arm64 macOS for webrtc. r=froydnj 2020-08-13 13:20:04 +00:00
signaling Bug 1650696 - P4. Remove the expectation for a MediaDataDecoder to work on a specified TaskQueue. r=jolin 2020-08-17 23:52:21 +00:00
trunk Bug 1658397 - Add gn configs for arm64 macOS for webrtc. r=froydnj 2020-08-13 13:20:04 +00:00
.gclient
.gclient_entries
moz.build Bug 1634675 - Remove webrtc-gtests r=drno,froydnj 2020-05-20 19:59:45 +00:00
webrtc.mozbuild