Local STT CUDA failure mid-transcribe CPU fallback
Cluster 111929. Data as of
Nothing open on GitHub. Fix merged in #112167 on 16 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #112167. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #112167. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a bug where local Whisper STT hard-fails on Windows when the CUDA runtime is unavailable mid-transcription, rather than falling back to CPU, along with fixes to add that retry/fallback behavior.
Open issues0
Open PRs0
Fixes on record
-
#112167 fix(stt): local whisper falls back to CPU when the CUDA runtime fails mid-transcribe (#111929, #105295, salvage #103848)
files:
contributors/emails/[redacted:email],tests/tools/test_transcription_tools.py,tools/transcription_tools.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#111933 fix(stt): retry lazy CUDA failures on CPU · merged via another change →
a1cbed3,#112167
Closed issues · 1
- Closed#111929[Bug]: Local STT hard-fails on Windows without the CUDA runtime - mid-transcribe fallback never fires (v0.21.3)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #112167
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 16 Sep 2026