microsoft / microsoft/vscode

VSCode 1.136 Debug Configuration Provider crashes Extension Host when extra parameters are passed for vscode.DebugConfiguration type

Open
#334,564 2 comments 0 reactions 1 assignee Claimed by @vijayupadya View on GitHub
stale triage-needed
Dominant language
TypeScript
Stars
193k
Forks
42.4k
PR merge metrics
PR metrics pending

Description

Edit: This is a problem in the debug configuration provider. I'm not sure if there was a type change from 1.135 to 1.136, but any extra parameters passed for debug configuration cause the extension host to crash. My code snippet below works when I just stick with the three properties for type, name, and request.

```typescript
// works when minimal
await vscode.debug.startDebugging(folder, {
type: 'idl',
name: 'IDL',
request: 'launch',
});
```

---

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

- VS Code Version: 1.136
- OS Version: Windows 11

With the update to 1.136 yesterday, I'm noticing issues launching debug sessions from within VSCode. There are two places where I am seeing this:

1. Extension development - when I run run an extension from source, the debug session in the host process drops occasionally and orphans the debug window, putting it in a bad state and preventing GitHub Copilot from working in the development window. This has been occurring more frequently over the past month or so, never happened before.
2. I'm no longer able to launch a debug session from my custom extension. In VS Code 1.135 everything works as expecte, but in 1.136 the extension host immediately terminates when this command is issues to VSCode through the API:

```typescript
// launch the debug configuration
console.log('start debugging');
try {
// ------PROBLEM HERE-----
await vscode.debug.startDebugging(
folder,
copy(DEFAULT_IDL_DEBUG_CONFIGURATION),
);
console.log('Debugging session should be launched');
} catch (err) {
console.log('Error');
console.log(err);
}
```

One thing of note, my extension auto-creates the debug configuration JSON payload (it is not in a file on disk) and, after this command is launched, we usually have debug start => resolve debug configuration => launchRequest in the debug adapter. I placed debug logs in those providers and they are never called

To show this, here's a short video of my complete workflow with the crash:

https://github.com/user-attachments/assets/23dac8c3-8dce-4cf5-b738-21cb5f618b2b

And here's what the Extension Host logs look like during a crash:

```
2026-09-04 11:15:23.468 [info] Extension host terminating: received terminate message from renderer
2026-09-04 11:15:23.492 [error] Error calling provideChatSessionProviderOptions for handle 0: Canceled
2026-09-04 11:15:23.492 [error] Error calling provideChatSessionProviderOptions for handle 0: Canceled
2026-09-04 11:15:23.495 [error] ProxyResolver#resolveProxy DIRECT Canceled: Canceled
at new rS (file:///c:/Users/username/AppData/Local/Programs/Microsoft%20VS%20Code/a44adf7f53/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:435:152801)
at i._remoteCall (file:///c:/Users/username/AppData/Local/Programs/Microsoft%20VS%20Code/a44adf7f53/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:435:158885)
at r..s.charCodeAt.r. (file:///c:/Users/username/AppData/Local/Programs/Microsoft%20VS%20Code/a44adf7f53/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:435:155638)
at Gg.resolveProxy (file:///c:/Users/username/AppData/Local/Programs/Microsoft%20VS%20Code/a44adf7f53/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:541:82586)
at Object.resolveProxy (file:///c:/Users/username/AppData/Local/Programs/Microsoft%20VS%20Code/a44adf7f53/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:674:25856)
at useProxySettings (c:\Users\username\AppData\Local\Programs\Microsoft VS Code\a44adf7f53\resources\app\node_modules.asar\@vscode\proxy-agent\out\index.js:277:16)
at c:\Users\username\AppData\Local\Programs\Microsoft VS Code\a44adf7f53\resources\app\node_modules.asar\@vscode\proxy-agent\out\index.js:214:13
at c:\Users\username\AppData\Local\Programs\Microsoft VS Code\a44adf7f53\resources\app\node_modules.asar\@vscode\proxy-agent\out\index.js:1134:13
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
```

Happy to provide anything else that is needed.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.