Skip to content

Voice replies can crash in the macOS audio render callback #473

Open

Description

@johnmatthewtennant

Problem

Berd 0.5.43 can crash during repeated local voice replies on macOS. This also reproduced in a later development build. It predates the microphone restart warning change in #472.

Reproduction

On macOS 26.6.2 (25G83), use Parakeet STT and Pocket TTS. In the captured reproduction, input was BlackHole 2ch 0.7.1, output was Apple Virtual Sound Device, and a separate AVAudioPlayer helper injected generated speech directly into BlackHole. The output and injected input used separate devices.

Start a voice conversation and ask “What is two plus three? Please answer in one short sentence.” Wait for the spoken answer, then repeat twice. Hang up, start another call and repeat the sequence.

The unmodified, Block-signed and notarized released 0.5.43 app completed two full three-reply cycles, then crashed after playback started for the second reply of the third cycle. The earlier development candidate crashed on an additional reply after a restart. This is intermittent. The reproduction establishes the failure with virtual audio routing; physical microphone and output devices have not been tested.

Crash report

Released app report: Berd-2026-11-05-211923.ips, process Berd PID 3441, version 0.5.43, bundle xyz.block.berd. The signature was verified before launch: Developer ID Application: Block, Inc. (EYF346PHUG), with a stapled notarization ticket. No app files were modified during the release run.

Exception: EXC_BAD_ACCESS / SIGSEGV
KERN_INVALID_ADDRESS at 0x0000000000000008

_Block_copy + 56
AUHALOutputUnit_RenderNotifyCallback(void*, unsigned int*, AudioTimeStamp const*, unsigned int, unsigned int, AudioBufferList*) + 44
CoreAudio (two frames without symbols)
HALC_ProxyIOContext::IOWorkLoop()
invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int)
HALC_IOThread::Entry(void*)
_pthread_start
thread_start

A native build of the exact pre-fix parent e7bc9336911bc1273d094bbbfd2eba2f898e0e65 also reproduced the crash on the third reply of its fourth three-reply cycle, on the same Mac and unchanged routing. Its native and frontend source are from that parent; it reuses the preserved candidate’s byte-identical backend and CLI sidecars, distribution runtime configuration and ad-hoc signing. Its report is Berd-2026-11-05-212431.ips, PID 19970, version 0.6.5.

Both baselines and the earlier development candidate have the same exception, fault address and faulting stack. The release failure also establishes that ad-hoc signing is not necessary for this crash. The crash is in Berd's process, rather than the speech-injection helper. Application versus framework or virtual-device root cause remains undetermined. The application has native render observers and engine teardown code; this is an investigation lead, not an established cause.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions