[BUG] Windows11 - Crash during wizard voice capture test
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Start by reproducing the onboarding voice-capture test on Windows 11: press Ctrl + Space, speak, then release it and observe the crash after the audio file is saved. Read the crash report for fluidvoice.exe and note that it identifies ucrtbase.dll and exception code 0xc0000409; the payload names no source files or tests. Done means dictation completes after releasing Ctrl + Space without crashing.
Written by the indexing model from the issue text.
Description
Describe the bug
FluidVoice crashes during the onboarding wizard "FluidVoice is ready" test. The audio is captured then when the Ctrl + Space is released it crashes during dictation. The audio file is saved to disk but no voice-to-text dictation.
Reproduction steps
- Open FV
- Go through onboarding wizard
- On "FluidVoice is ready" page press Ctrl + Space
- Talk
- Release Ctrl + Space
- Dictating.... then crashes (no dictation)
Expected behavior
voice-to-text dictation should work
Actual behavior
Application crash
App Version
0.0.2.0
macOS Version
Windows 11 Enterprize
Architecture
Intel
Logs or crash report
Faulting application name: fluidvoice.exe, version: 0.0.2.0, time stamp: 0x6a4e23f8
Faulting module name: ucrtbase.dll, version: 10.0.22621.3593, time stamp: 0x10c46e71
Exception code: 0xc0000409
Fault offset: 0x000000000007f6fe
Faulting process id: 0x0x2200
Faulting application start time: 0x0x1DD0F20D218F58C
Faulting application path: C:\Users\*****\AppData\Local\FluidVoice\fluidvoice.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 94ad386e-32f2-4de8-a9b9-972fb157422e
Faulting package full name:
Faulting package-relative application ID:
Screenshots or screen recording
No response
- Dominant language
- Swift
- Stars
- 11.9k
- Forks
- 863
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 37
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from altic-dev/FluidVoice
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
altic-dev/FluidVoice#1191 ·
Maintainers usually reply within 1 day
-
[BUG] File transcription skips audio chunks shorter than one secondPossibly taken @sabbah13 claimed this 8 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
altic-dev/FluidVoice#1161 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
altic-dev/FluidVoice#1225 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 44/100
altic-dev/FluidVoice#1223 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
altic-dev/FluidVoice#1222 ·
Maintainers usually reply within 1 day
All issues in altic-dev/FluidVoice
Similar issues
-
product / auth product / databases product / functions product / messaging product / storage product / vcs
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
storage: eliminate force-unwraps and fatalError in continueStreamingUploadPossibly taken @chingor13 claimed this today. Openapi: storage type: cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
googleapis/google-cloud-swift#1527 ·
Maintainers usually reply within 1 day
-
ci-failure ci:assertion test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openwatersio/slackwater-ios#811 ·
Maintainers usually reply within 1 day
-
ai-assisted
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
swiftlang/swift-testing#1979 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day