VS Code Speech not Working in Visual Studio Code Insiders Edition (Version: 1.106.0-insider)

[genidma]

🔎 Search existing issues to avoid creating duplicates.

• Check

🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders

• Check On the Insiders version.

💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information.

• Negative: There is a separate bug (outside of Visual Studio Code...) whereby Wayland does not like Chromium Browser or Chromium Based browsers. As soon as a Chromium based browser is launched on Wayland. By Default 'GPU acceleration' is enabled on the browser and this is causing the entire Operating System to halt/crash. Sometimes REISUB works and often it doesn't (Thus requiring a hard reset).

Hence, if I actually click on 'Create on Github' in order to 'Report Issue', this is most likely going to cause my system to crash. I am not sure why the system is not loading up these pages in Firefox.

🔧 Launch with code --disable-extensions to check.
Does this issue occur when all extensions are disabled?: Yes/No

• I tried this, but this takes User back to the 'Issue Reporter' UI. So see above, bug for Wayland (Chromium Browser GPU enabled by default causing system crash)

🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause.

• Already tried that. The process went through a cycle of disabling extension in chunks. Finally isolating the problem to the VS Code Speech extension. However, see above.

📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this.

• VS Code Version: 1.106.0-insider
• OS Version: Linux x64 6.14.0-34-generic

Version: 1.106.0-insider
Commit: facd8c5
Date: 2025-10-27T09:47:48.225Z
Electron: 37.7.0
ElectronBuildId: 12597478
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.14.0-34-generic

mindset:echo $XDG_CURRENT_DESKTOP
ubuntu:GNOME
mindset:echo $XDG_SESSION_TYPE
wayland
mindset:lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 25.04
Release: 25.04
Codename: plucky
mindset:uname -a
Linux mram-desktop 6.14.0-34-generic #34-Ubuntu SMP PREEMPT_DYNAMIC Wed Sep 17 09:21:29 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
mindset:

Steps to Reproduce:

1. Install VS Code Speech in VS Code Insiders Edition from the Extensions section
2. Ensure that the system (Ubuntu) recognizes the microphone input and change the settings according. As well, ensure that the microphone is plugged into the microphone jack (red)
3. Create a new empty file in VS Code Insiders and use keyboard combo 'ctrl+alt+V' in order to bring up the VS Code Speech extension
4. A microphone icon shows up in VS Code Insiders edition. However, no voice is converted to text
5. Github Copilot Voice Chat feature is also not working.

Thx

[bpasero]

To figure out more about this issue related to voice recognition, can you do this:

• close all instances of VS Code
• open a terminal / console
• define an VSCODE_SPEECH_LOGS_PATH environment variable pointing to a non existing file in a folder that exists
  • on Windows: set VSCODE_SPEECH_LOGS_PATH=<path to file>
  • on macOS/Linux: export VSCODE_SPEECH_LOGS_PATH=<path to file>
• start VS Code from that terminal / console by typing code (or code-insiders)
• set log level to trace for the extension (see [1])
• open the output channel for the extension (see [2])
• try to reproduce the issue that you had seen with voice recognition or keyword activation

Can you then share the output from the extension output channel as well as any log files in the folder of VSCODE_SPEECH_LOGS_PATH. Thanks!

[1]

[2]

[genidma]

• Extension keeps crashing.
  • I followed the steps you recommended
  • Next, I opened a new/blank file in VS Code Insiders and did a 'ctrl+alt+v' in order to enable VS Code Speech dictation mode

Output

2025-10-28 18:32:11.358 [trace] [vscode-speech-0] aborting keyword-recognition session
2025-10-28 18:32:11.390 [trace] [vscode-speech-0] stopped keyword-recognition session
2025-10-28 18:32:16.282 [trace] [vscode-speech-1] starting keyword-recognition session
2025-10-28 18:33:20.817 [trace] [vscode-speech-2] starting speech-to-text session (language: en-US, model: Microsoft Speech Recognizer en-US FP Model V9, path: /home/redacted/.vscode-insiders/extensions/ms-vscode.vscode-speech-0.16.0-linux-x64/assets/stt)
2025-10-28 18:33:55.016 [trace] [vscode-speech-0] starting speech-to-text session (language: en-US, model: Microsoft Speech Recognizer en-US FP Model V9, path: /home/redacted/.vscode-insiders/extensions/ms-vscode.vscode-speech-0.16.0-linux-x64/assets/stt)
2025-10-28 18:34:26.720 [trace] [vscode-speech-0] starting speech-to-text session (language: en-US, model: Microsoft Speech Recognizer en-US FP Model V9, path: /home/redacted/.vscode-insiders/extensions/ms-vscode.vscode-speech-0.16.0-linux-x64/assets/stt)
2025-10-28 18:36:03.926 [trace] [vscode-speech-0] starting speech-to-text session (language: en-US, model: Microsoft Speech Recognizer en-US FP Model V9, path: /home/redacted/.vscode-insiders/extensions/ms-vscode.vscode-speech-0.16.0-linux-x64/assets/stt)
2025-10-28 18:36:30.930 [trace] [vscode-speech-0] starting speech-to-text session (language: en-US, model: Microsoft Speech Recognizer en-US FP Model V9, path: /home/redacted/.vscode-insiders/extensions/ms-vscode.vscode-speech-0.16.0-linux-x64/assets/stt)
2025-10-28 18:36:30.933 [trace] [vscode-speech-0] aborting speech-to-text session

• Separately, while trying to "Start Voice Chat' for Github Copilot Chat. Same error as above.

[bpasero]

Can you please follow the steps in https://github.com/Microsoft/vscode/wiki/Native-Crash-Issues to get at more details around the crash and attach the result here? Thanks!

Robo (@deepak1556) fyi ext host crash

[genidma]

Creating a crash report

• Close all instances of VSCode.
• Run code --crash-reporter-directory from the command line.
  • code-insiders --crash-reporter-directory /tmp/vscode-insiders-2025-10-29-1600UTC
    as the location where crash dumps will be saved.
• Run code-insiders instead of code if the issue is occurring on the Insiders version. ✅
• Take the steps that lead to the crash.
• Check for a *.dmp file in that folder.
  located inside of the 'pending' folder

mindset:pwd
/tmp/vscode-insiders-2025-10-29-1600UTC
mindset:tree
.
├── attachments
├── client_id
├── completed
├── new
├── pending
│   ├── 03a6b808-23fb-4acd-b8d0-77d43a16aac1.dmp
│   ├── 03a6b808-23fb-4acd-b8d0-77d43a16aac1.meta
│   ├── 358b8f0c-78ea-40c3-b40b-3421b8b8fefb.dmp
│   ├── 358b8f0c-78ea-40c3-b40b-3421b8b8fefb.meta
│   ├── 628feb2b-eed0-4966-8211-047fcf4129d8.dmp
│   ├── 628feb2b-eed0-4966-8211-047fcf4129d8.meta
│   ├── de63f05a-1141-4bf8-ba3e-bf10c66b085c.dmp
│   └── de63f05a-1141-4bf8-ba3e-bf10c66b085c.meta
└── settings.dat

5 directories, 10 files

• Send the *.dmp file back to us, either by email, or by creating a zip archive containing it and attaching the zip to the GitHub issue.
  • *.dmp files only

vscode-insiders-2025-10-29-1600UTC.zip *.dmp 
  adding: 03a6b808-23fb-4acd-b8d0-77d43a16aac1.dmp (deflated 88%)
  adding: 358b8f0c-78ea-40c3-b40b-3421b8b8fefb.dmp (deflated 87%)
  adding: 628feb2b-eed0-4966-8211-047fcf4129d8.dmp (deflated 88%)
  adding: de63f05a-1141-4bf8-ba3e-bf10c66b085c.dmp (deflated 89%)

vscode-insiders-2025-10-29-1600UTC-dmp-files-only.zip

- [x]  *.dmp files with *.meta files (Not sure why this text is being formatted as code. fyi only)

mindset:zip vscode-insiders-2025-10-29-1600UTC-dmp-with-meta.zip *.dmp *.meta
  adding: 03a6b808-23fb-4acd-b8d0-77d43a16aac1.dmp (deflated 88%)
  adding: 358b8f0c-78ea-40c3-b40b-3421b8b8fefb.dmp (deflated 87%)
  adding: 628feb2b-eed0-4966-8211-047fcf4129d8.dmp (deflated 88%)
  adding: de63f05a-1141-4bf8-ba3e-bf10c66b085c.dmp (deflated 89%)
  adding: 03a6b808-23fb-4acd-b8d0-77d43a16aac1.meta (deflated 56%)
  adding: 358b8f0c-78ea-40c3-b40b-3421b8b8fefb.meta (deflated 56%)
  adding: 628feb2b-eed0-4966-8211-047fcf4129d8.meta (deflated 56%)
  adding: de63f05a-1141-4bf8-ba3e-bf10c66b085c.meta (deflated 56%)

vscode-insiders-2025-10-29-1600UTC-dmp-with-meta.zip

[genidma]

Remote Extension Host Crashes

• I am not sure if this applies to me? Because the Extensions are loaded locally on the vscode-insiders edition
  • If I need to follow through these steps also, just let me know
• Fyi only: I am trying to find out more information about what 'Remote Extension Host' really does. But I think the portion that serves web/app e.t.c for vscode on Microsoft's website is having issues at the moment (16:41 UTC till 17:04 UTC and continuing)
  • https://code.visualstudio.com/api/advanced-topics/extension-host
    • I think the code.visualstudio .. website is serviced by Azure (I am not sure) and there appears to be an Azure outage right now

- Screenshot above via https://status.cloud.microsoft/

Service Unavailable

HTTP Error 503. The service is unavailable.

• I asked Google

The Remote Extension Host is the component of Visual Studio Code that runs extensions on a remote machine, allowing you to develop as if the code were local. When you use a Remote Development extension, such as Remote-SSH or Dev Containers, VS Code automatically installs a small server component, called the VS Code Server, on the remote environment. The Remote Extension Host runs on this server.

Ah yes. This is when an ssh-extension is installed (e.t.c I am thinking the same for docker and I have yet to tinker with docker with vscode). For ssh, I have noticed that doing so results into vscode running and installing vscode-server on the target machine and if memory serves me correctly. By doing so, the local instances on VS Code (Chat and other extensions) can interact with the remote machines. But this does not apply for me at the moment.

• Going back to the instructions link you had shared
  • The man page for ulimit says that this utility has been deprecated

DESCRIPTION
       Warning:  this  routine is obsolete.  Use getrlimit(2), setrlimit(2), and sysconf(3) instead.  For the shell
       command ulimit, see bash(1).

Google AI powered search clarifies

ulimit is still functional but limited. The command-line utility continues to work for setting resource limits for the current shell and processes it starts. However, it is obsolete for system services on modern Linux distributions that use systemd.

For system services, use systemd unit files. Instead of ulimit, configure resource limits directly within the .service unit file for a service (e.g., in /etc/systemd/system/myservice.service). Use directives like MemoryMax= and CPUQuota=.

For system-wide or user-specific defaults, edit limits.conf. To apply limits globally or to specific users, use the /etc/security/limits.conf file. This is useful for user logins, but it is often ignored by systemd-managed services.

Google AI powered search (after different iteration) recommends and fyi only.

Instead of
ulimit, use:

• systemd unit files for services and background processes.
  

• /etc/security/limits.conf for interactive user session limits.
  

• prlimit for modifying the limits of a running process.
  

• cgroups for advanced, fine-grained control over process groups.