Microsoft/vscode

VS Code is ignoring the environment setting for node js --max-old-space-size

Open

#231,076 创建于 2024年10月11日

在 GitHub 查看
 (9 评论) (0 反应) (1 负责人)TypeScript (74,848 star) (10,221 fork)batch import
buggood first issuehelp wantedterminal-processwindows

描述

VS Code is ignoring the environment setting for node js --max-old-space-size

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

  • VS Code Version: 1.94.2
  • Node.js: v20.18.0
  • OS Version: Edition Windows 11 Pro Version 23H2 Installed on ‎9/‎10/‎2023 OS build 22631.4317 Experience Windows Feature Experience Pack 1000.22700.1041.0

Steps to Reproduce:

  1. Setup node options for user/system Image

  2. Open cmd to validate Image

  3. Open ps to validate Image

  4. Open VS Code to validate - value is ignored/overwritten with something else Image

Thanks, Regards, Evgeny

贡献者指南

技术栈
typescriptelectronnodejs
领域
desktop
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
blocked
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Node.js environment variablesVS Code process model
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Investigate how VS Code's Node.js processes handle environment variables. Check if VS Code explicitly sets ` max old space size` via command line arguments, overriding the `NODE OPTIONS` env var. Look at the source in `src/vs/base/node/processes.ts` and any `launch.json` configurations. Determine if the issue is in the Electron main process or the integrated terminal's Node.js process. Reproduce the issue and verify the behavior difference between cmd/PS and VS Code.