microsoft / microsoft/vscode-cmake-tools

CMake stops working: "cmake .viewLog" or others says command not found

Open
#4,279 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

more info needed
Dominant language
TypeScript
Stars
1.7k
Forks
546
Avg merge
2d 16h
Merged PRs (30d)
32

Description

### Brief Issue Summary

Hello.

- C++ real world project, mid-large size company one.
- Ubuntu 20.04 WSL
- It has been happening for multiple releases. Latest one also: 1.19.52
- Bisecting cames up to CMakeTools extension.

Extension seems to stop working randomly. Sometimes it takes a few hours, other it crashes.

_NODE_OPTIONS has been added in ~/.bashrc already._

Error messages:
- Any CMake command stops working, so I can't get or execute the log diagnostics or any other.

```
cmake.logDiagnostics: command not found:
cmake.viewLog command not found`
```

**Workaround**
The workaround is to restart vscode and opening the project again.

Any guidance or help how I can provide you more info to help work this out?

### CMake Tools Diagnostics

```shell

```

### Debug Log

```shell

```

### Additional Information

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the CMake Tools command failure in VS Code on Ubuntu 20.04 WSL, using the reported cmake.viewLog and cmake.logDiagnostics entry points. Capture the CMake Tools Diagnostics and Debug Log, which are currently empty, and compare behavior before and after restarting VS Code. Done means the commands remain available after the extension has been running for hours.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, typescript, vscode
Domain
build-system, devtools, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.