Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Language server exits with code 0 and restarts repeatedly (1.35.4, Windows 11)

未关闭
#14,841 4 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@sean-mcmanus 已经在做这个了。

开始于 2026年10月22日。

评估

这个 Issue 还没有评估数据。

描述

bug Language Service more info needed reliability
Environment
  • OS: Windows 11 Enterprise, 10.0.28000.3231
  • VS Code: 1.141.2
  • C/C++ extension: 1.35.4 (pre-release)
  • Settings: "C_Cpp.maxConcurrentThreads": 2, "C_Cpp.workspaceParsingPriority": "low"
What happens

The notification "The language server crashed. Restarting..." appears again and again. It happened five times in about 34 hours in one VS Code session, from 2026-10-20 to 2026-10-22. Each time the output channel shows the same sequence:

[Error - 8:56:31 PM] Client cpptools: connection to server is erroring.
write EPIPE
[Error - 8:56:31 PM] Server process exited with code 0.
[Error - 8:56:31 PM] Client cpptools: connection to server is erroring.
Cannot call write after a stream was destroyed
[Error - 8:56:32 PM] The language server crashed. Restarting...

The other four were at 9:57 PM, 12:52 AM, 1:28 AM and 5:05 AM. Two of them begin directly with "Server process exited with code 0." and have no write EPIPE line.

The server exits with code 0 rather than a signal, so no crash call stack is shown.

Workspace
  • A large Rust workspace with git submodules: about 4,400 tracked files, of which 7 are C/C++ files (C headers for a C ABI).
  • C/C++ is not edited during these periods.
  • Long cargo builds and test runs with two jobs often run at the same time, so the machine is under load.
Next

I have set "C_Cpp.loggingLevel": "Debug" and will add the debug log from the next occurrence to this issue. Tell me if a different capture would help more, for example a specific logging setting or a dump configuration for an exit with code 0.

— Xmip (https://github.com/IlleNilsson)

主要语言
TypeScript
星标
6.2k
派生
1.7k
平均合并
1 天 16 小时
30 天内合并 PR
20

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

microsoft/vscode-cpptools 的其他 Issue

查看 microsoft/vscode-cpptools 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。