develop ← emezeske:pr/audiodevicemanager-zero-buffer-size-hang
opened 07:51PM - 10 Aug 26 UTC
If an audio device reports a current buffer size of 0, CallbackMaxSizeEnforcer's… chunking loop computes a block length of 0 and never advances, so the audio thread spins forever. This can happen when a device is mid-reconfiguration, for example the JACK backend reports 0 when its client is unavailable.
With this change the enforcer emits a silent block instead and recovers on the next audioDeviceAboutToStart(), which restores the real block size.