With some Cubeb backends (e.g. PulseAudio), a state callback indicating a stream error may be triggered synchronously during stream initialization when opening a device that is no longer present. The client side is not able to receive these callbacks during initialization, so log and ignore them. The stream initialization will fail normally and initiate any required cleanup.
With some Cubeb backends (e.g. PulseAudio), a state callback indicating a stream error may be triggered synchronously during stream initialization when opening a device that is no longer present. The client side is not able to receive these callbacks during initialization, so log and ignore them. The stream initialization will fail normally and initiate any required cleanup.
This should address BMO 1801049.