# PR: AudioDeviceManager: Fix a hang when a device reports a zero buffer size

**URL:** <https://forum.juce.com/t/pr-audiodevicemanager-fix-a-hang-when-a-device-reports-a-zero-buffer-size/69278>\
**Category:** Development\
**Created:** [August 10, 2026, 8:07pm UTC](https://forum.juce.com/t/pr-audiodevicemanager-fix-a-hang-when-a-device-reports-a-zero-buffer-size/69278 "2026-08-10T20:07:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![emezeske](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/emezeske/32/15528_2.png) [@emezeske](https://forum.juce.com/u/emezeske)\
**Post date:** [August 10, 2026, 8:07pm UTC](https://forum.juce.com/t/pr-audiodevicemanager-fix-a-hang-when-a-device-reports-a-zero-buffer-size/69278/1 "2026-08-10T20:07:35Z")

</div>

> <https://github.com/juce-framework/JUCE/pull/1703>
>
> 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.
