microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
160.19k stars 28.06k forks source link

"VS Code Speech" Extension Crashes on Activation #218202

Open fussbanana opened 6 days ago

fussbanana commented 6 days ago

Does this issue occur when all extensions are disabled?: Yes/No

Bugreport: "VS Code Speech" Extension Crashes on Activation

Description

The "VS Code Speech" extension for VS Code crashes as soon as it is activated. The crash occurs during the speech-to-text session after recognizing the keyword "Hey Code".

Steps to Reproduce

  1. Activate the "VS Code Speech" extension.
  2. Start a keyword-recognition session.
  3. Say the keyword "Hey Code".
  4. The speech-to-text session starts and then crashes with an error code 0x8 (SPXERR_FILE_OPEN_FAILED).

Expected Behavior

The extension should recognize the keyword and execute the speech-to-text functionality without errors.

Actual Behavior

The extension recognizes the keyword, attempts to start the speech-to-text session, and then crashes with the error code 0x8 (SPXERR_FILE_OPEN_FAILED).

Environment

Extension Version

Error Log

2024-06-25 16:51:19.561 [trace] [vscode-speech-0] starting keyword-recognition session
2024-06-25 16:51:34.672 [trace] [vscode-speech-0] keyword recognized: Hey Code
2024-06-25 16:51:34.675 [trace] [vscode-speech-0] aborting keyword-recognition session
2024-06-25 16:51:34.753 [trace] [vscode-speech-1] starting keyword-recognition session
2024-06-25 16:51:34.754 [trace] [vscode-speech-2] starting speech-to-text session (language: de-DE, model: Microsoft Speech Recognizer de-DE FP Model V2, path: /home/sascha/.vscode/extensions/ms-vscode.vscode-speech-language-pack-de-de-0.4.0/assets/stt)
2024-06-25 16:51:34.808 [error] [vscode-speech-2] speech-to-text error: Exception with an error code: 0x8 (SPXERR_FILE_OPEN_FAILED)
[CALL STACK BEGIN]
...
[CALL STACK END]
2024-06-25 16:51:34.809 [trace] [vscode-speech-2] disposed speech-to-text session
2024-06-25 16:51:41.858 [trace] [vscode-speech-2] aborting speech-to-text session

Directory Structure and Permissions

/home/sascha/.vscode/extensions/ms-vscode.vscode-speech-language-pack-de-de-0.4.0/assets/stt
.
├── ciphone.list
├── config.yaml
├── decoder.quantuint8.onnx
├── de-de_explicitPuncRules.txt
├── de-de_ProfanityList.enc
├── encoder.quantint8.onnx
├── joint.quantuint8.onnx
├── lid.quants8u8.onnx
├── lp.config
├── model_onnx_quant.config
├── model_sentence
├── model_word
├── prongen
│   ├── grph1031.lxa
│   ├── l1031.phn
│   ├── lsr1031.lxa
│   └── tn1031.bin
├── sr.ini
├── svad.quantized.onnx
├── tokens.list
└── version.txt

Permissions

drwxrwxr-x 3 sascha sascha 4096 Jun 25 16:46 speechmodel.de-DE.cpu.2.0.40100365

Additional Information

I have verified that all files in the directory /home/sascha/.vscode/extensions/ms-vscode.vscode-speech-language-pack-de-de-0.4.0/assets/stt are present and readable.

Steps Taken

Request for Assistance

Could you please help resolve this issue? Any guidance or fixes would be greatly appreciated.

Thank you!

Best regards, [Sascha]

fussbanana commented 3 days ago

Hello dear development team,

I hope this message finds you well. I wanted to follow up on the status of my previously submitted bug report. Since I haven't received any feedback yet, I wanted to ensure that the report has not been overlooked.

bpasero commented 3 days ago

Does it work when the language is english and not german in settings?

fussbanana commented 3 days ago

No, that makes no difference. I have tried all sorts of variations. It's probably not because of the German language package.

Benjamin Pasero @.***> schrieb am Sa. 29. Juni 2024 um 08:12:

Does it work when the language is english and not german in settings?

— Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode/issues/218202#issuecomment-2197999636, or unsubscribe https://github.com/notifications/unsubscribe-auth/BILO2SESQGMQFMNNLFTTZSDZJZF4XAVCNFSM6AAAAABJ4PZQKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJXHE4TSNRTGY . You are receiving this because you authored the thread.Message ID: @.***>