You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Crash (SIGTRAP) in bundled sherpa-onnx/onnxruntime: BFCArena requests a single 2 GiB allocation, Chromium allocator shim traps and kills the whole app #7925
Orca crashed with EXC_BREAKPOINT (SIGTRAP) on a Node worker thread running the bundled sherpa-onnx speech recognizer. ONNX Runtime's BFCArena attempted a single 2 GiB allocation (x19/x21 = 0x80000000) while growing its memory pool during inference. Chromium's allocator shim refuses single allocations that large and intentionally traps (brk 0), taking down the entire app, including all open worktrees and agent sessions.
Environment
Orca 1.4.128 (Electron 42.3.3)
macOS 27.0 (26A5378j), Mac16,5 (M4 Max, 128 GB)
libonnxruntime.1.23.2.dylib / sherpa-onnx-darwin-arm64 as shipped in Contents/Resources/node_modules
The frames above operator new resolve to bogus nearest-symbol names in the stripped Electron binary (ares_dns_rr_get_ttl + 3284868 etc.); they are Chromium's allocator shim / OOM crash handler executing an intentional brk 0 after rejecting the oversized request.
Register state at trap: x19 = x21 = 0x0000000080000000 (2 GiB request), esr = 0xf2000000 (Breakpoint) brk 0.
Analysis
The offline (batch) recognizer decodes the whole audio buffer in one call, so encoder tensor sizes scale with audio length. BFCArena grows by doubling, so a long enough capture doubles the arena past 2 GiB.
Chromium's allocator shim hard-caps single allocations; instead of returning nullptr it calls its immediate-crash path. One oversized tensor allocation on a worker thread therefore kills the whole app. The machine itself was under no memory pressure (128 GB).
Suggested fixes
Chunk/stream audio into the offline recognizer (or use the streaming recognizer) so tensor sizes are bounded regardless of capture length.
Possibly related, from the same setup: in the Orca iOS app, the microphone button on the standard Apple keyboard is not usable. Tapping it dismisses dictation immediately, so Apple's built-in speech-to-text can never be used as input. That leaves Orca's bundled recognizer as the only voice path, which is the component that crashed above.
If system dictation (iOS keyboard mic, and macOS dictation on desktop) worked as a plain text input, users would not need to depend on the in-app sherpa-onnx pipeline at all. Worth checking whether something in the input view (e.g. a custom text field re-grabbing first responder, or inputView/focus handling in the webview) is cancelling the keyboard dictation session.
Activity
dogangok commentedon Jul 9, 2026
Possibly related, from the same setup: in the Orca iOS app, the microphone button on the standard Apple keyboard is not usable. Tapping it dismisses dictation immediately, so Apple's built-in speech-to-text can never be used as input. That leaves Orca's bundled recognizer as the only voice path, which is the component that crashed above.
If system dictation (iOS keyboard mic, and macOS dictation on desktop) worked as a plain text input, users would not need to depend on the in-app sherpa-onnx pipeline at all. Worth checking whether something in the input view (e.g. a custom text field re-grabbing first responder, or
inputView/focus handling in the webview) is cancelling the keyboard dictation session.AmethystLiang commentedon Jul 9, 2026
will be in next release