Amazon Q for VS Code: Catastrophic Memory Leak — Extension Unusable

OS: Windows_NT x64 10.0.19045
Visual Studio Code: 1.100.2
Amazon Q Extension: 1.69.0
Node.js: 20.19.0
Electron: 34.5.1

Issue Summary
After updating to the latest Amazon Q extension (v1.69.0) on VS Code (1.100.2, Windows 10 x64), Amazon Q is completely unusable due to an apparent catastrophic memory leak in its language server processes.

Symptoms:

On every launch, logs show repeated warnings like:

[warning] childProcess: Process 25000 exceeded memory threshold: 605204.00 MB
[warning] childProcess: Process 36428 exceeded memory threshold: 310296.00 MB
(Sometimes different PIDs and numbers, always > 300 GB RAM.)

After these warnings, all attempts to use Amazon Q features fail with:

Encountered an unexpected error when processing the request, please try again.
Request ID: [varies, e.g., 934d31c3-5fd0-4965-b43f-6d6aaf3d40a6]
Reinstalling, clearing extension folders and caches, and resetting settings does not resolve the issue.

Happens even in a clean workspace with no open projects.

Early logs often show authentication/connection issues, but those eventually resolve—the memory leak persists regardless.

Steps to Reproduce
Install Amazon Q for VS Code (v1.69.0) on Windows 10 x64, VS Code 1.100.2.

Open VS Code with any (or no) project.

Watch the Output/Log (Amazon Q and AWS Toolkit).

Try to use Amazon Q chat, code suggestions, or any agentic feature.

Observed Log Output (Sample)
[warning] childProcess: Process 25000 exceeded memory threshold: 605204.00 MB
[warning] childProcess: Process 36428 exceeded memory threshold: 310296.00 MB
Encountered an unexpected error when processing the request, please try again.
Request ID: 934d31c3-5fd0-4965-b43f-6d6aaf3d40a6
Additional relevant log snippets:

[error] CodeWhisperer: Error when fetching feature configs Error: No connection found

[Warn - 1:32:09 PM] No workspace folders set during initialization

[warning] telemetry: invalid Metric: "languageServer_setup" emitted with missing fields: id

Troubleshooting Already Attempted
Cleared all Amazon Q and AWS Toolkit extension folders from .vscode/extensions, workspaceStorage, and globalStorage.

Reinstalled Amazon Q and AWS Toolkit.

Restarted VS Code and system.

Tried with different and empty projects.

Disabled all other extensions.

Ensured Node.js is current (20.19.0).

Expected Behavior
Amazon Q should function normally and not consume impossible amounts of memory or crash its child processes. All chat/code features should be available.

Actual Behavior
Amazon Q’s child processes exceed hundreds of GB of RAM (impossible on my system), crash, and the extension becomes unusable—every action results in the “unexpected error” dialog.

Environment Details
OS: Windows_NT x64 10.0.19045

VS Code: 1.100.2

Amazon Q Extension: 1.69.0

Node.js: 20.19.0

Electron: 34.5.1

Request
Please escalate this issue to engineering ASAP. This is a showstopper bug and makes Amazon Q for VS Code unusable on Windows.

Reproduce with Amazon Q 1.69.0, VS Code 1.100.2, Windows 10 x64, and a clean workspace, then inspect the Amazon Q and AWS Toolkit output for the child-process memory warnings and request errors. Done means the child processes stay within normal memory limits and chat, code suggestions, and agentic features work without the unexpected-error dialog.

Written by the indexing model from the issue text.